Professional Documents
Culture Documents
Fy = v
2
A sin u
Chapter 5 Controlling the Dynamic Solution 5-7
Harmonic Analysis
Input Excitation Frequencies
Harmonic Analysis Excitation Frequencies
Starting Frequency
First frequency in the users defined excitation frequency range. The defined harmonic displacements and forces will have
the form: A*cosine(wt+p), where A is the amplitude of the force or displacement, p is the phase angle, and e is the
frequency of the loading. Real and imaginary solutions will be developed for each frequency in the defined range (from
which any phased solution can be calculated). For an entered frequency range to be valid there must be at least a starting
frequency. All frequencies are entered in Hertz.
Ending Frequency
Last frequency in the users defined excitation frequency range. If omitted then it defaults to the Starting frequency.
Increment
Frequency increment. If omitted then defaults to 1.0 Hz.
5-8 Controlling the Dynamic Solution
The frequencies for harmonic excitation are taken from each frequency range defined by the user. Individual frequencies for
excitation are computed using a DO LOOP type of logic as follows:
X = STARTING FREQUENCY
5 CONTINUE
COMPUTE SOLUTION FOR FREQUENCY X
X = X + INCREMENT
IF( X .LT. ENDING FREQUENCY+0.001) GO TO 5
Using this logic the user can determine exactly which frequencies in a specified frequency range will be analyzed. The sign
of the frequency increment may be modified by CAESAR II to properly step from the users starting frequency to his ending
frequency.
Either the starting frequency, the ending frequency, or the frequency increment may be given as a fraction or a whole part
with fraction.
Any number of user comment lines may be included. There can be any number of line entries in the Excitation frequency
data.
EXAMPLES:
Find harmonic solutions for the following group of equipment speeds:
100 rpm (Warm up speed)
400, 800, 1200, 1600, 2000, 2400, 2800, 3200 rpm. Speeds passed through very slowly while coming up to operating
speed.
3600 rpm. Operating speed.
Rotations per minute convert to cycles per second by dividing by 60. Frequency excitation would be input.
WARM UP SPEED (DIVIDE RPM BY 60 TO GET HERTZ) 100/60
BRINGING TURBINE ON-LINE (DIVIDE RPM BY 60 TO GET HERTZ) 400/60 3200/60 400/60
OPERATING SPEED (DIVIDE RPM BY 60 TO GET HERTZ) 3600/60
A low frequency field vibration exists in the piping system at about 3 Hertz. Define a 3 Hertz excitation:
APPROXIMATE FIELD OBSERVED EXCITATION FREQUENCY (HZ) 3
The response of the piping system when the dynamic load was applied at 3 Hertz was almost zero. This was true regardless
of the magnitude of the dynamic load (i.e. the maximum conceivable varying pressure load was applied, and there were still
no appreciable dynamic displacements when the excitation frequency was 3 Hertz). Apply the dynamic load over a range of
frequencies around 3 Hertz and see if any dynamic response can be observed.
GROUP OF FREQUENCIES AROUND THE FIELD GUESSED AT
3 HERTZ EXCITATION. THE EXCITATION FREQUENCIES
DEFINED BY THE INPUT BELOW ARE:
(2.5, 2.6, 2.7, ..., 3.3, 3.4, 3.5) HZ.
2.5 3.5 0.1
Load Cycles
Number of cycles expected for this loading. If entered, this signals to CAESAR II that the harmonic load case should be
treated as a fatigue stress case with the allowable stress based on the number of anticipated cycles.
Chapter 5 Controlling the Dynamic Solution 5-9
Harmonic Forces and Displacements
Harmonic Forces
Either the Harmonic Forces or the Displacements must be entered in addition to the Excitation Frequency Data. Click the
Harmonic Forces button to bring up a window like that shown below. Click the + button on the toolbar to add a harmonic
force.
Force
Amplitude of the harmonic force. The form of the harmonic forcing function is: F(t) = A*cosine( et-|), where F(t) is the
force as a function of time. A is the maximum amplitude of the dynamic force. e is the frequency of the excitation (in
radians per second), and p is the phase angle (in radians). Enter the force in the units shown. These units are taken from
the current set which resides on the file UNITS.FIL.
Direction
Enter the line of action of the force as either X, Y, Z, or as direction cosines or direction vectors. The format for direction
cosines is (cx,cy, cz), i.e. (0.707,0.0,0.707). The format for direction vectors is (vx, vy, vz), i.e.. (1,0,1).
5-10 Controlling the Dynamic Solution
Phase
Enter the phase angle in degrees. The harmonic loading can start with its maximum load at time equal to zero, or the
harmonic load can start with its maximum at any time between zero and t=2*pi/w seconds. The phase angle is the method
used to specify this time shift in the dynamic load waveform. The phase angle can be calculated from the time shift using
the equation: p(degrees) = 180tw/pi, where t is given in seconds and w is given in radians per second. Most frequently the
phase angle is entered as either zero or 90. The phase specification is most useful when defining eccentric loads on rotating
equipment. Some of the examples that follow discuss common applications of the phase angle input. The phase angle is a
required input. If the phase angle is zero, then 0.0 must be entered !
Start Node
The node where the force is to act. This entry is required. If entered without a Stop Node and Increment, then this node must
exist in the piping system. If entered with a Stop Node and Increment, then the range of nodes identified by the loop must
include at least one node in the piping system.
Stop Node
Used as a part of a range of nodes force loading command. This entry is optional.
Increment
Used as a part of a range of nodes force loading command. This entry is optional.
EXAMPLES
It is assumed that a pressure pulse traveling in the line between nodes 95 and 100 causes the line to shake at about 2 hertz.
The magnitude of the pressure loading (See the examples for calculating forces from pressures) is estimated to be about 460
lb. The pressure wave travels from 95 to 100. The harmonic force to model this load is shown as follows. Note that the
magnitude is divided by 2 because the total variation in the dynamic load is a function of the cosine, which varies from -1 to
1. To find the true response magnitudes from a positive only harmonic load pulse, a static solution with 460/2 lb. acting in
the plus X direction would have to be superimposed on the static 460/2 lb. solution to provide the constant shifting of the
load axis (i.e. as defined in the following example, there will exist a negative load at node 95 due to the negative sign on the
cosine). The pressure pulse will always be positive and so a negative load will never exist. The superposition of the 460/2
static solution makes sure that the dynamic load (and probably the resulting displacements) are always positive.
460 LB PRESSURE LOAD AT 2 HERTZ 460/2 X 0.0 95
A pump is shaking in the X-Y plane. The pump axis is along the global Z axis. The magnitude of the dynamic load is
computed to be 750 lb. from the manufacturers provided masses and eccentricities. Apply this rotating equipment loading
on the inline pump at node 350. The X and Y loads are 90 degrees out of phase with one another. When the X load is at its
maximum the Y load is zero, and when the Y load is at its maximum the X load is zero.
ESTIMATED ECCENTRIC LOAD ON INLINE PUMP DOH-V33203001
750 X 0.0 350
750 Y 90.0 350
Chapter 5 Controlling the Dynamic Solution 5-11
Harmonic Displacements
Displacement
Amplitude of the harmonic displacement. The form of the harmonic displacement function is: D(t)=(A)*cosine(et-|), where
D(t) is the displacement as a function of time, A is the maximum amplitude of the dynamic displacement. e is the
frequency of the excitation (in radians per second), and | is the phase angle (in radians). Enter the displacements in the
units shown.
Direction
Enter the line of action of the displacement as either X, Y, Z, or as direction cosines or direction vectors. The format for
direction cosines is (cx,cy,cz), i.e (0.707,0.0,0.707). The format for direction vectors is (vx, vy, vz), i.e. (1,0,1).
Phase
Enter the phase angle in degrees. The harmonic displacements can start with its maximum displacement at time equal to
zero, or the harmonic displacements can start with its maximum displacements at any time between zero and t + 2 t/e
seconds. The phase angle is the method used to specify this time shift in the dynamic load waveform. The phase angle can
be calculated from the time shift using the equation: | (degrees) = 180te/t, where t is given in seconds and e is given in
radians per second. Most frequently the phase angle is entered as either zero or 90. The phase specification is most useful
when defining eccentric displacements on rotating equipment. Some of the examples that follow discuss common
5-12 Controlling the Dynamic Solution
applications of the phase angle input. The phase angle is a required input. If the phase angle is zero, then 0.0 must be
entered!
Start Node
Node where the dynamic displacement is defined. If the node is a supported node, then the dynamic displacement will be
assumed to act at the support point. If the node is not supported, then the dynamic displacement will be assumed to describe
the exact motion of the pipe at that point. This differentiation only becomes important when the node is supported by a
flexible restraint. For example, node 55 is supported in the Y direction by a restraint having a stiffness of 5000 lb./in. A
harmonic displacement is also specified at node 55, in the Y direction. In this case, the harmonic displacement does not
describe the displacement that is attached to 55!
Harmonic Displacements at Compressor Flange
0.008 Y 0.0 330
0.003 Z 0.0 330
If the Start Node is entered without a Stop Node and Increment, then this node must exist in the piping system. If the Start
Node is entered with a Stop Node and Increment, then this range of nodes must include at least one node in the piping
system.
Stop Node
Used as a part of a range of nodes force displacement loading. This entry is optional.
Increment
Used as a part of a range of nodes force displacement loading. This entry is optional.
EXAMPLES
A large ethylene compressor shakes the node exiting the compressor flange in the Y direction a field measured 8 mils, and
in the Z direction an amount equal to 3 mils. Define these dynamic displacements. The displacements are assumed to be
simultaneous, with no phase shift. This is because the load causing the displacements is believed to be the compressor
plunger moving in the X, or axial direction. (The displacements are skewed because the piping configuration entering
the compressor is itself skewed.)
Applying estimated eccentric forces to the pump described in the harmonic force example did not produce the
displacements witnessed in the field. Field personnel have measured the dynamic displacements in the vertical (Y) and
transverse (Z) directions at the pump piping connections. The centerline of the pump, at the intersection of the
horizontal suction and vertical discharge is node 15. The magnitude of the Z displacement was measured to be 12 mil.
The magnitude of the Y displacement was measured to be 3 mils. It is assumed that the vibration is due to the rotation
of the pump shaft, and so the Z and Y loads will be taken to be 90 degrees out of phase.
HARMONIC DISPLACEMENTS MODELING PUMP VIBRATION ON THE INLINE PUMP DOH-V33203001.
MODELLING THE PUMPS
DYNAMIC LOAD WITH FORCES DID NOT RESULT IN THE
DISPLACEMENTS WITNESSED BY FIELD PERSONNEL. NOW TRY
IMPOSING THE DISPLACEMENTS AND SEE WHAT THE RESULTING
FORCES ARE. ALSO CHECK TO SEE IF THE ATTACHED PIPING
MOVES AROUND AS EXPECTED.
Z MAGNITUDE OF THE LOAD - ZERO PHASE SHIFT
0.012 Z 0.0 15
Y MAGNITUDE OF THE LOAD - 90 DEG. PHASE SHIFT
0.003 Y 90.0 15
Chapter 5 Controlling the Dynamic Solution 5-13
Response Spectra / Time History Load Profiles
Spectrum Definitions
Name
Can be any 24-character identifier. This name is associated with a particular spectrum or load profile. The complete
definition of a shock includes its name, range type, ordinate type, range interpolation method, ordinate interpolation method,
and the shock data point table. Everything but the shock data point table can be entered here. There are 14 predefined
spectra for which no extra definitions are required and they are:
El Centro
5-14 Controlling the Dynamic Solution
For the El Centro California N-S component taken from Biggs, Introduction to Structural Dynamics, and applies for
systems with 5-10 percent critical damping.
REG. GUIDE 1.60
1.60H.5 and 1.60V.5
1.60H2 and 1.60V2
1.60H5 and 1.60V5
1.60H7 and 1.60V7
1.60H1.0 and 1.60V10
Each of these spectra defines respectively the horizontal and vertical components for 0.5, 2, 5, 7, and 10 percent critically
damped systems. Associated with each of these spectra is a value for the Maximum ground acceleration at the site, the ZPA.
(Zero Period Acceleration) This value defaults to 0.5 g and can be changed on the control parameter spreadsheet.
Uniform Building Code
UBCSOIL1
UBCSOIL2
UBCSOIL3
These spectra represent the normalized (horizontal) response spectra for three soil types provided in Figure 23-3 of the
Uniform Building Code, (1991 Edition).
Note The spectrum name (or load profile) can be preceded by a (#) sign. The (#) sign instructs CAESAR II to read the
spectrum table from a file having the same name as the spectrum with no extension.
Entering the spectrum table in an ASCII file allows several jobs to access the same spectrum table data without the user
having to retype it for each job. If data is to be read directly from within the Dynamic Output then click the Data Points
button and enter the appropriate Range and Ordinate values.
Range Type
This entry defines the table range, or horizontal axis, and can be either Period, Frequency, or "Time". If the range
type is Period then the spectrum table data must be entered in seconds. If the range type is Frequency then the spectrum
table data must be entered in Hertz, (cycles per second). Time may be used for Time History load profiles only, and must be
entered in milliseconds (ms).
Ordinate Type
This entry defines the spectrum table ordinate, or vertical axis, and can be either Acceleration, Velocity, Displacement or
Force (multiplier). Any part of the word for the ordinate type can be spelled out, but only the first letter is required. Note
that acceleration units are length per second squared. Users may enter the spectrum table ordinate in gs by selecting
acceleration as the ordinate type and then using a shock scale factor of 386, for length units of inches. For Time History
load profiles, the only valid ordinate type is Force (multiplier).
Range Interpolation
Interpolation between range values may be done logarithmically or linearly (valid input is LOG or LIN). See the examples
shown for additional discussion.
Ordinate Interpolation
Interpolation between ordinate values may be done logarithmically or linearly (valid input is LOG or LIN). See the
examples shown for additional discussion.
One job may have any number of different spectrum types and definitions.
Chapter 5 Controlling the Dynamic Solution 5-15
Special FORCE spectrum data files are created by the DLF Spectrum generator. See the documentation covering this item
later in this chapter.
When a new job is started up the 14 predefined spectra is already included in the spectrum definition list. Any combination
of these predefined spectra may be used as is, deleted or used with any other user defined spectra.
ASCII files that contain spectrum table data can contain comment lines starting with an asterisk just like regular terminal
entered data lines. The user is encouraged to include the basic spectrum data definitions in the comments for each ASCII
spectrum file. See the example that follows.
Example
The job requires that the El Centro shock be applied in the X and Z directions using a factor of 1.0, and in the Y direction
using a factor of 0.667.
There is no spectrum definition required for this shock. El Centro is a predefined spectrum. All of its shock data resides in
the CAESAR II shock database.
The job requires the use of the Nuclear Regulatory Guide 1.60 shock loads. At a maximum acceleration value of 0.25 gs,
analysis is to be performed using 1.0 times the horizontal and vertical components of the shock as specified in Reg. Guide
1.60.
There is no spectrum definition required for either of these two shock loads. The Reg. Guide 1.60 shock spectra are
predefined. The user must only specify the maximum acceleration (ZPA) of 0.25 gs on the control parameter spreadsheet,
and must use the reg. guide spectra which correspond to the anticipated system damping. Lower damping values mean
more conservative results.
The job requires a shock spectrum that is given by the client and developed for the site. A plot of the spectrum appears as
follows. The horizontal axis is period and the vertical axis is acceleration. From the variation of the numbers along each axis
it can be seen that a logarithmic interpolation for each axis should be used. Because the shock name is NOT preceded by
a (#) sign the user will have to enter the points for this spectrum during this interactive input session.
BENCHNO4 PERIOD ACCELERATION LOG LOG
All jobs on a particular project require the use of the spectrum table shown as follows. Since we only want to type the
spectrums data points in one time, the points will be entered into a file named BENCH1. The ASCII file BENCH1 can be
created using any standard editor or the CAESAR II text editor. The listing of the ASCII file for BENCH1 is shown following
the plot of the spectrum.
The spectrum definition input for pointing to this file is:
#BENCH1 PERIOD ACCEL LOG LOG
Listing of ASCII file BENCH1:
SPECTRUM FOR NUCLEAR BENCHMARK NO.1. THIS SPECTRUM IS
TO BE USED FOR ALL LINES ON PROJECT 1-130023-A03.
FILENAME = BENCH1
RANGE TYPE = PERIOD (SECONDS)
ORDINATE TYPE = ACCELERATION (IN./SEC./SEC.)
INTERPOLATION FOR BOTH AXES = LOGARITHMIC.
FILE PREPARED BY M.NASH JANUARY 15, 1987
PERIOD(SEC) ACCELERATION(IN/SEC/SEC)
5-16 Controlling the Dynamic Solution
0.1698
E-02
0.1450E
+03
0.2800E
-01
0.3800E
+03
0.5800E
-01
0.7750E
+03
0.7100E
-01
0.7750E
+03
0.9100E
-
01
0.4400E
+03
0.1140E
+00
0.1188E
+04
0.1410E
+00
0.1188E
+04
0.1720E
+00
0.7000E
+03
0.2000E
+00
0.8710E
+03
0.2500E
+00
0.8710E
+03
0.3230E
+
00
0.4000E
+03
Response Spectrum / Time History Profile Data Point Input
Data points for user-defined spectra may be entered through the menu option Tools /Spectrum Data Points.
Range
Spectrum table range value. There should be at least one range-ordinate pair for each spectrum.
Ordinate
Spectrum table ordinate value. There should be at least one range ordinate pair for each spectrum.
Values may be entered in exponential format (i.e. 0.3003E+03, or 0.3423E-03, or 0.3003E3,...), or can have explicit
multiplication or division (i.e. 4032.3/386, or 1.0323*12). Sufficient data points should be entered to fully describe the
spectrum or load profile.
Chapter 5 Controlling the Dynamic Solution 5-17
There can be any number of line entries in the spectrum data. Data may also be read from a file using the Read From File
button.
Force Response Spectrum Definitions
The CAESAR II DLF Spectrum Generator takes the time waveform of some excitation and converts it into a frequency
domain dynamic load factor (DLF) curve. The frequency domain dynamic load factor curve is written to a hard disk file and
can be read directly by CAESAR II as a FORCE response spectrum curve. Input for the Pulse Table Generator is shown as
follows.
DLF/Spectrum Table Generator
Force Spectrum Name
The force spectrum generator creates an ASCII file containing the force spectrum that corresponds to the input time history
waveform.
Maximum Table Frequency
Enter the maximum frequency that should exist in the CAESAR II generated spectrum table. This value seldom needs to be
greater than 100 Hz. If piping frequencies greater than 100 Hz are found in the system and included in the spectrum
analysis, then the spectrum value at 100 Hz would be used. The user can decide which frequencies are important, and
therefore how high the frequency must go, by looking at the solution participation factors and the animated mode shapes.
Typically only the lower frequencies contribute to the system displacements, forces and stresses.
Number of Points in the Table
This is the number of points CAESAR II will generate for the spectrum table. Usually 15 to 20 points are sufficient. These
points are distributed in a cubic relationship starting from zero hertz.
Create Table
When the Create Table button is clicked, a dialog box will appear with the input table as displayed below. Enter the Time /
Force data and click the OK button to create the DLF curve on the hard drive.
5-18 Controlling the Dynamic Solution
Input Table Dialog
Time
Enter the points that describe the time waveform to be modeled. Units for this table are milliseconds. (1000 milliseconds
equal one second.)
Force
Enter the forces that correspond to the points on the force/time curve. Units are as shown. Note that the absolute magnitude
of the force is not important, only the form of the time history loading is important. The actual maximum value of the
dynamic load is taken from the force pattern defined in: SPECTRUM/TIME HISTORY FORCE SETS.
There can be any number of line entries in the Excitation frequency data.
Chapter 5 Controlling the Dynamic Solution 5-19
Building Spectrum / Time History Load Cases
Time History Load Cases
Spectrum /Time History Profile
Enter the name of the shock that was defined during the Time History Definitions phase of the input. This may be any type
of spectra, user defined, predefined, or read from a file. (DO NOT PRECEDE THE SPECTRUM NAME WITH A # HERE,
EVEN IF THE SPECTRUM TABLE WAS READ FROM AN ASCII DATA FILE!) Any number of shocks can be listed
here. Individual contributions can be of any shock type or definition.
Factor
Constant by which to multiply the shock table. Usually 1.0, or if the spectrum table data points were read in units of gs, to
convert to in/sec/sec then this factor would be 386. There are several examples that follow which illustrate various
applications of this value.
Direction
Defines the direction of application of the shock. To define an earthquake type of loading, CAESAR II must know what the
earthquake shock looks like, which comes from the shock spectrum table. CAESAR II must also know in which direction
this shock acts. Typically a shock load case will be comprised of three shock components. One acts in the X direction, one
5-20 Controlling the Dynamic Solution
in the Z, and one in the Y. The combination of each of these three shocks defines the earthquakes dynamic loading of the
piping system.
Skewed directions may be entered by giving a direction cosine or direction vector. Skewed shock contributions are entered
when the piping or structural system appears particularly sensitive to a shock along a skewed line. This most often occurs
when a majority of the piping system lies along a 45 degree line in the horizontal plane. An example shock input for this
type of system is shown among the examples on the following pages.
Any number of shock components can act in the same direction. i.e. there can be two X direction components. This usually
occurs with independent support shock contributions where one X direction component would apply to one support group
and another X direction component would apply to a different support group. (However, there can be two shock
components in the same direction without having independent support contributions defined. This would just involve
defining two shock contributions in the same direction without start, stop, or increment node entries.)
In the simplest form of force spectrum loading there is only a single shock component in the load case, i.e. there is only a
single line of input on the load case screen. When there are multiple lines of input on the load case screen, as when the user
is analyzing a traveling pressure wave that impacts different elbow-elbow pairs, there can be many components to the shock
load case. The combination of responses from each of these shock loading components can be established in one of two
ways. If the Direction field is the same for each load component, then the Directional Combination method will be used to
combine the responses from each load component. If the Direction field is different for each load component, then the
spatial combination method will be used to combine the responses from each load component. The difference between
Spatial and Directional combination methods is that Directional combinations are always made before Modal combinations,
while Spatial combinations can be made before or after Modal combinations, (it is user controlled). The default is to
perform the Modal combinations before Spatial combinations. Either Spatial or Directional combinations can be made using
the ABS or SRSS method. Some of the following force spectrum examples illustrate these differences.
Note: Since Time History combinations are all algebraic (in-phase), this entry is used as nothing more than a label during
this type of analysis.
Force Set #
If the Spectrum/Load Profile Name describes a Force-type spectrum (rather than displacement, velocity, or acceleration),
then the fourth entry in the load case screen is the force set number. This force set number corresponds to the loads entered
in the Force Sets option. Examples shown on the following pages illustrate this application. Note that if a force set # is
entered, the last three fields must be left blank!
Start Node
Start node, stop node, and increment are only used to define the component of an independent support shock (ISM). This is
a shock component that applies only to a group of support points. For example, different shock spectrum may have been
generated for rack level piping and for ground level piping. In this case the rack supports would be subject to one shock
excitation (influenced by the racks response to the earthquake), and the ground level supports would be subject to a
different shock excitation (not influenced by the rack). In this case, one node range would be used to define the rack support
shock contributions and another would be used to define the ground support shock contributions. The range of nodes
defined by the start node, stop node, and increment must include at least one support point.
Stop Node
Part of the range of nodes. If omitted, defaults to the start node. See the examples that follow for clarification.
Increment
Part of the range of nodes. If omitted, defaults to 1. See the examples that follow for clarification.
Anchor Movement (Earthquake Only)
This entry is only used for independent support movements. It is used to specify the absolute displacement of the restraints
included in this shock case. This displacement is used to calculate the pseudostatic load components representing the
Chapter 5 Controlling the Dynamic Solution 5-21
relative displacement of the individual restraint sets. If omitted, the default is taken from the lowest frequency entry of the
response spectrum: specified displacement, velocity/frequency, or acceleration/frequency
2
(where frequency is angular
frequency).
Directives
A number of directives can be set for each individual load case using the Directives button. These parameters are optional
extensions to the global options set for all load cases on the Control Parameter spreadsheet. Typically users will not need
to specify any of these options.
Directional Combination Method. Similar directional components will be combined using either the ABS or the SRSS
summation method. If there are two shock components in the X direction, the components from each shocks effect on the
system will be summed absolutely. Directional combinations are performed before all other combinations. (There are three
types of combinations: DIRECTIONAL, SPATIAL AND MODAL). The default DIRECTIONAL combination method is
ABS.
Modal Combination Method.
Modal (Group) Modal components will be combined using the Reg. Guide 1.92 GROUPING method. CAESAR II uses
the Revision 1, February 1976 issue of the Regulatory Guide 1.92. See the discussion of the SPATIAL(ABS) directive for a
description of the relationship that exits between modal and spatial response combinations.
Modal (10%) Modal components will be combined using the Reg. Guide 1.92 10% method.
Modal (DSRSS) Modal components will be combined using the Reg. Guide 1.92 Double Square Root of the Sum of the
Squares method. Damping is assumed to be equal for all modes and is taken from the control parameter spreadsheet.
Modal (ABS) Modal components (response quantities) will be combined absolutely. (i.e. the absolute value of each
response quantity will be summed.)
Modal (SRSS) Modal components will be combined using the square root of the sum of the squares method of
combination.
Spatial Combination Method (ABS or SRSS). Spatial components will be combined using the ABS summation method.
There are typically three spatial components in a single earthquake type shock load case. The three usual excitation
directions are the X, Y, and Z global axes. (Although there can be any number of spatial components along any global or
skewed axes.)
5-22 Controlling the Dynamic Solution
Spatial or Modal Combination First. Modal before Spatial summations are Independent. An Independent shock is one
where the X, Y, Z components are random and temporally independent of one another. (i.e. time histories for each
directional component of the shock are not equal.) Spatial before Modal summations are Simultaneous. A simultaneous
shock is one where the X, Y, and Z components are random, but temporarily the same (i.e. time histories for each
directional component of the shock are equal).
Pseudostatic Combination Method (ABS or SRSS). Pseudostatic components for each ISM are added into the response
quantities either absolutely or using the SRSS method of combination. Pseudostatic combinations are performed after all
spatial and modal combinations. The user can deactivate the inclusion of pseudostatic component from the control
parameter spreadsheet.
Missing Mass Combination Method (ABS or SRSS). Missing mass components for each shock load are added into the
response quantities either absolutely or using the SRSS method of combination. The user can deactivate the inclusion of
missing mass components from the control parameter spreadsheet. Missing mass components are added in following modal
summation.
Stress Type (EXP). Stress type for the load case is set using the stress type drop list. If FATigue is selected, the expected
number of load cycles must be entered. The user can change the default stress type dynamic loads to any of the allowed
stress types in CAESAR II. Available stress types are EXP, SUS, OCC, OPE, and FAT. The OCC or occasional stress type is
the default.
The entry of node groups causes a pseudostatic component of the shock to be created. This pseudostatic contribution
can be added or omitted from the final shock loading effects. Additional parameters can be entered on the control
parameter spreadsheet.
The order of input of the shock contributions is not important, and has no bearing on the results.
There is no limit to the number of shock load cases the user can define. The dynamic output processor lets the user
decide which of the Spectrum/Time History Load Cases he wants to process.
Any number of user comment lines may be included. There can be any number of line entries in the spectrum data.
EXAMPLES
Define a shock load case that excites the piping system with a vibration of one times the El Centro earthquake in the X
direction, one times the El Centro earthquake in the Z, and 0.667 times the El Centro earthquake in the Y direction.
ELCENTRO 1 X
ELCENTRO 1 Z
ELCENTRO 0.667 Y
Define a shock load case that excites the piping system with the horizontal and vertical components of the Reg. Guide 1.60
shock spectra for a 2 percent critically damped system. The maximum ground acceleration should be 0.22 gs.
The maximum ground acceleration is set on the control parameter spreadsheet and has no effect on the shock load case
definitions.
1.60H2 1 X
1.60H2 1 Z
1.60V2 1 Y
Define a shock load case that is comprised of the users' shocks BENCH1 and BENCH2. BENCH1 should act in the X and Z
directions, and shock BENCH2 should act in the Y direction. The scale factor for all shocks is 1.0.
BENCH1 1 X
BENCH2 1 Y
BENCH1 1 Z
Chapter 5 Controlling the Dynamic Solution 5-23
One of the shock load cases for this particular job should excite the piping system along a line that is 45 degrees off of the
global axes in the horizontal plane. It is suspected that this direction of excitation will yield the worst possible results. Apply
the user defined shock BENCH1 in the horizontal direction and BENCH2 in the vertical direction.
BENCH1 1 (1,0,1)
BENCH1 1 (-1,0,1)
BENCH2 1 Y
Define a shock load case that excites the piping system with a vibration of two times the El Centro earthquake in the X, Y,
and Z directions. There should be two shock load cases in this job. The first should use an independent summation and the
second a simultaneous.
The load cases would be defined as shown. (There are several ways to accomplish the same objective here using parameters
on the control parameter spreadsheet, etc. Only the method using the explicit definition of the load case combination
method will be presented.) Remember that independent summation means MODAL then SPATIAL, and simultaneous
means SPATIAL then MODAL.
LOAD CASE 1 SHOCK CONTRIBUTIONS - CAESAR IIs title
MODAL(GROUP), SPATIAL(SRSS), MODAL COMBINATIONS FIRST
ELCENTRO 2 X
ELCENTRO 2 Y
ELCENTRO 2 Z
LOAD CASE 2 SHOCK CONTRIBUTIONS - CAESAR IIs title
SPATIAL(SRSS), MODAL(GROUP), SPATIAL COMBINATIONS FIRST
ELCENTRO 2 X
ELCENTRO 2 Y
ELCENTRO 2 Z
Define a shock case that has the user defined spectrum 1DIR acting in the Z direction only. Set the stress type for the case
to be operating and use modal summations before spatial summations. Note that there is no mention of modal or spatial
summations in the load data shown as follows (only the stress type). This is because modal summation first is the
CAESAR II default and would have to be changed on the control parameter spreadsheet for it not to still apply.
1DIR 1 Z
STRESSTYPE(OPE)
The support nodes 5, 25, 35, 45, and 56 are pipe shoes sitting on concrete foundations. The support nodes 140, 145, 157,
160, and 180 are second level rack supports, i.e. pipe shoes sitting on structural steel beams in the second level of the rack.
The ground level shock spectrum name is GROUND04, and the second level rack spectrum name is RACKLEVEL2-
04. Set up the shock load case to define these independent support excitations. Note that an option exists on the control
parameter spreadsheet to neglect the pseudostatic component of the Independent Support Excitation. Assume that this
option is activated. The default is to include the pseudostatic component in an absolute (ABS) summation method.
5-24 Controlling the Dynamic Solution
GROUND LEVEL EXCITATION
GROUND04 1.0 X 5,56,1
GROUND04 1.0 Y 5,56,1
GROUND04 1.0 Z 5,56,1
RACK LEVEL 2 EXCITATION
RACKLEVEL2-04 1.0 X 140,180,1
RACKLEVEL2-04 1.0 Y 140,180,1
RACKLEVEL2-04 1.0 Z 140,180,1
Set up a shock load case, and define all combinations options explicitly. Use the same shock components as defined in the
above example, except assume that the pseudostatic component is to be added using the SRSS combination method. Also
change the modal summation method is SRSS. (This is the recommended method.) Note that when the modal summation
method is SRSS it doesn't matter whether modal or spatial combinations are performed first. The order is only a factor when
closely spaced modes are considered as in the grouping, ten percent, and DSRSS methods.
MODAL(SRSS),PSEUDOSTATIC(SRSS),SPATIAL(SRSS)
GROUND LEVEL EXCITATION
GROUND04 1.0 X 5,56,1
GROUND04 1.0 Y 5,56,1
GROUND04 1.0 Z 5,56,1
RACK LEVEL 2 EXCITATION
RACKLEVEL2-04 1.0 X 140,180,1
RACKLEVEL2-04 1.0 Y 140,180,1
RACKLEVEL2-04 1.0 Y 140,180,1
The last elbow in the relief valve piping is at node 295. The spectrum name: BLAST contains the DLF response spectrum
for this relief valves firing. SPECTRUM/TIME HISTORY FORCE SET #1 contains the load information and its point of
application. Show the load case input that would provide the most conservative combination of modal results. (Because
there is only a single loading there is no consideration given to spatial or directional combinations.)
Shock Name, Factor, Direction, and Force Set #
ABSOLUTE MODAL SUMMATION, ONLY A SINGLE LOADING
COMPONENT AND SO NO CONSIDERATION GIVEN TO SPATIAL OR
DIRECTIONAL COMBINATIONS.
BLAST, 1, X, 1
MODAL (ABS)
Use the same example above and combine the modes using the grouping method. This will produce the most realistic
solution.
BLAST, 1, X, 1
MODAL (GROUP)
There are two elbow-elbow pairs that are of significance in this job. Waterhammer loads act on the elbow at 40 in the X
direction and on the elbow at 135 in the Y-direction. In the SPECTRUM/TIME HISTORY FORCE SET input, force set #1
is defined as the load at 40 and force set #2 is defined as the load at 135. Add the response quantities from each load
component first, using an ABS summation, and then the resulting modal response quantities second, using the grouping
summation method. Two identical methods for achieving the same results are shown.
Chapter 5 Controlling the Dynamic Solution 5-25
Shock Name, Factor, Direction, and Force set #
BECAUSE THE DIRECTION INPUT IS THE SAME, I.E. X, FOR BOTH,
LOAD CONTRIBUTIONS, THE DIRECTIONAL COMBINATION METHOD
WILL GOVERN HOW THE HAMMER 40 AND HAMMER135 RESPONSES
ARE COMBINED.
HAMMER40, 1, X, 1
HAMMER135, 1, X, 2
DIRECTIONAL (ABS), MODAL(GROUP)
<or>
BECAUSE THE DIRECTION INPUT IS DIFFERENT, I.E. X AND Y,
THE SPATIAL COMBINATION METHOD WILL GOVERN HOW THE
HAMMER40 AND HAMMER135 RESPONSES ARE COMBINED. NOTE THAT
ON THE DIRECTIVE LINE THE SPATIAL DIRECTIVE COMES BEFORE
THE MODAL DIRECTIVE.
HAMMER40, 1, X, 1
HAMMER135, 1, Y, 2
SPATIAL(ABS), MODAL(GROUP)
5-26 Controlling the Dynamic Solution
Combining Static and Dynamic Results
Static/Dynamic Combinations
Load Case
Defines the static or dynamic load case that is to be a part of this combination case. The load case label must always start
with an S or a D for Static and Dynamic, and must be immediately followed by a load case number. Valid entries are: S1,
STATIC1, S3, STATIC3, D1, DYNAMICS1, S#1, D#1, ...etc... The user can use any length up to 24 characters to define
the load case label so long as the name starts in an S or a D, and ends in a valid load case number. For static load case
definitions, the static case must exist and have already been run (also, the S cant refer to a spring hanger design case). For
dynamic load case definitions, the dynamic load case number refers to the shock load case. Several examples are given as
follows.
Factor
This entry is required and multiplies the response quantities from the respective static or dynamic run.
<Directive Data>
The Stress Type drop list or the Directive button may be used to set optional extensions to global options set for all load
cases on the Control Parameter spreadsheet. Typically the user will not need to specify any of these options. Some of the
examples included on the following pages illustrate cases where these directives provide extra desired flexibility.
STRESSTYPE (EXP)
Chapter 5 Controlling the Dynamic Solution 5-27
STRESSTYPE (SUS)
STRESSTYPE (OPE)
STRESSTYPE (OCC)
STRESSTYPE (FAT)
The user can change the default stress type for the combination case to any of the four shown here. The default stress type is
OCC - occasional.
COMBINATION (SRSS)
COMBINATION (ABS)
Defines how the load cases listed are to be combined. The ABS method takes the absolute value of all displacement, force,
and stress data for each load case and adds them together. The SRSS method sums the square of all displacement, force, and
stress data for each load case and then takes the square root of the result.
Any number of separate static and dynamic cases can exist in the Combination Load Case list provided each reference
to a static or dynamic case is on a separate line.
The order of input of the load case definitions is not important, and has no bearing on the results.
Any number of user comment lines may be included.
Static cases alone can be combined without dynamic cases.
Dynamic cases alone can be combined without static cases.
EXAMPLES:
The static cases run in the job were:
1 = W+P1+D1+T1+F1 (OPE)
2 = W+P1+F1 (SUS)
3 = L1 - L2 (EXP)
The dynamic cases run in the job were:
1 = Operating Basis Earthquake
2 = 1/2 the Operating Basis Earthquake
The user must combine the Operating Basis Earthquake Stresses with the Sustained Static Stresses. The specification for
this combination case is:
STATIC2 1.0
DYNAMIC1 1.0
<or>
S2 1
D1 1
5-28 Controlling the Dynamic Solution
The static cases run in the job were:
1 = W + P1 + F1 (For hanger design)
2 = W + P1 + D1 + T1 + F1 (For hanger design)
3 = W + P1 + D1 + T1 + F1 (OPE)
4 = W + P1 + F1 (SUS)
5 = L3 - L4 (EXP)
There was one dynamic load case. The user is required to turn an occasional case that is the sum of the sustained and the
dynamic stresses using the SRSS Combination method and the ABS Combination method. Additionally, the user must
combine the expansion static case and the dynamic case using the SRSS Combination method. This is a total of three
combination load cases. Note that since the job had hanger design the first two static load cases cannot be used in a
combination case. The input for each case is shown as follows:
COMBINATION CASE 1:
* SRSS COMBINATION OF SUSTAINED AND DYNAMIC CASES
STRESSTYPE(OCC), COMBINATION(SRSS)
STATIC4 1
DYNAMIC1 1
COMBINATION CASE 2:
* ABS COMBINATION OF SUSTAINED AND DYNAMIC CASES
STRESSTYPE(OCC), COMBINATION(ABS)
STATIC4 1
DYNAMIC1 1
COMBINATION CASE 3:
* SRSS COMBINATION OF EXPANSION AND DYNAMIC CASES
STRESSTYPE(OCC), COMBINATION(SRSS)
STATIC5 1
DYNAMIC1 1
The static cases run in the job were:
1 = W+T1+P+D1+F1 (OPE)
2 = W+P+F1
3 = U1 (OCC) ... Static seismic simulation
4 = L1-L2
5 = ST2+ST3
Chapter 5 Controlling the Dynamic Solution 5-29
The user is instructed to perform an SRSS Combination of the static seismic case and both the sustained and operating
static cases. The combination case lists for these two cases would appear:
COMBINATION CASE 1:
COMBINATION(SRSS), STRESSTYPE(OCC)
STATIC2 1
STATIC3 1
COMBINATION CASES 2:
COMBINATION(SRSS), STRESSTYPE(OCC)
STATIC1 1
STATIC3 1
The following static load cases were run:
1 = W+P1+F1 (Hanger design restrained weight case)
2 = W+T1+F1+P1+D1 (Hanger design load case #1)
3 = W+T2+F1+P1+D1 (Hanger design load case #2)
4 = WNC+P1+F1 (Hanger design actual cold loads)
5 = W+T1+F1+P1+D1 (OPE)
6 = W+P1+F1 (SUS)
7 = L5-L6 (EXP)
Spectrum/Time History Load Cases 1 through 6 were defined by the client. The static sustained stresses are to be combined
with 1/2 the shock case 1 results, 1/2 the shock case 2 results, and 1.333 times the shock case 3 results. The combination
method is to be SRSS. A second combination case is to combine 1/2 the shock case 4 results, 1/2 the shock case 5 results,
and 1.333 times the shock case 6 results. These two combination load cases would be defined as shown as follows:
COMBINATION CASE 1:
COMBINATION(SRSS)
STATIC6 1
DYNAMIC1 1/2
DYNAMIC2 1/2
DYNAMIC3 1.333
<or>
COMB(SRSS)
S6 1
D1 0.5
D2 0.5
D3 1.333
COMBINATION CASE 2:
5-30 Controlling the Dynamic Solution
COMBINATION (SRSS)
STATIC6 1
DYNAMIC4 0.5
DYNAMIC5 0.5
DYNAMIC6 1.333
Chapter 5 Controlling the Dynamic Solution 5-31
Spectrum Time History
Force
Maximum value of the dynamic load applied at this point. Units are as shown. Note that the total applied force will be the
product of this value, the selected force value from the spectrum or load profile, and the factor entered for the load case.
Direction
Direction of the dynamic load. Can be entered as X, Y, or Z or direction cosines or direction vectors. Direction cosines are
entered in the form (cx,cy,cz), i.e. (0.707, 0, 0.707). Direction vectors are entered in the form: (vx, vy, vz), i.e. (1,0, and 1).
Node
Node number where the force acts.
Force Set #
Number to uniquely identify this particular force load pattern. See the examples that follow for clarification. This value
defaults to 1.
The general procedure for applying a force spectrum load is as follows:
1 Determine the pulse time history that acts at a single node or over a group of nodes. Only the pulse waveform must be
the same for all nodes in group, the maximum pulse amplitude may vary. For example, a particular shock load due to
ocean current loading acts over the nodes 5, 10, 15, 20, 25, and 30 on a production piping system, and the magnitude of
the dynamic loading is 50 lb. at 5, 100 lb. at 10, 200 lb. at 15, and so on up to 500 lb. at 30. Also the dynamic load as a
function of time at each point is equal to half of a sine wave with a period of one second. Even though the magnitude of
the dynamic load varies over the nodes from 5 to 30, the pulse waveform does not (The pulse waveform is the half sine
wave, and its shape is the same for each node). Thus the group of nodes from 5 to 30 can be included in the same force
set #, each node having a different dynamic force magnitude.
2 Using the CAESAR II DLF Spectrum Generator build a DLF vs. frequency file for the time-pulse waveform.
3 Using the Spectrum Definitions option, define the DLF vs. frequency file just created as a Force spectrum data file with
linear interpolation along the frequency axis and linear interpolation along the ordinate axis. (The DLF Spectrum
Generator builds a standard shock table file. Until the type of shock data in the file is described to CAESAR II, the file
cant be used.) Remember to precede the shock name with a # sign when defining it in the Spectrum Definitions so
that CAESAR II knows to read the shock table from the data file.
4 Determine the maximum force magnitude that acts on each node subject to the pulse load.
5 Using the Force Set Editor specify the maximum amplitude of the dynamic load, its direction, and the nodes it acts on.
6 Build the Spectrum/Time History Load Cases by entering the Force spectrum name (this is the name that is preceded by
the # sign, defined in the Spectrum Definitions editor), the table multiplication factor (usually 1.0), a direction (this is
only a label used for output processing and should be characteristic of the shock, the actual force spectrum loads can act
in multiple directions), and the Force Set #. (The Force Set # refers to the force pattern defined in the Force Spectrum
Editor in step 5 above.) It is step 6 that defines the link between the force spectrum and the force loading pattern.
7 Setup any other parameters needed to run the spectrum analysis for this job. Perform error checking, and once there are
no fatal errors, run the job.
For a Time History analysis, the load profile used in step 2 would be entered directly in step 3, with the rest of the process
remaining the same.
Any number of user comment lines may be included. There can be any number of line entries in the Force spectrum data.
5-32 Controlling the Dynamic Solution
If there are multiple force spectrum components in a single dynamic load case, the user should be particularly careful with
the combination method selected. In this case, the same rules that cover earthquake shocks and components apply to force
spectrum shocks and components.
EXAMPLES:
The nodes 5, 10, and 15 define a cantilever pipe leg that is part of an offshore production platform. The dynamic load as a
function of time is equal to a half sine wave. The waveform is the same for all three nodes, but the maximum dynamic load
on node 5 is 5030 lb., on node 10 is 10,370 lb., and on node 15 is 30,537 lb. Three force sets are to be built for this problem.
One is with the dynamic loads acting in the X direction. One is with the dynamic loads acting in the Z direction, and the
third is with the dynamic loads acting simultaneously in the X an Z directions. The force spectrum input data for this job is
as follows:
* X DIRECTION HALF SINE WAVE/CURRENT LOADING
5030 X 5 1
10370 X 10 1
30537 X 15 1
* Z DIRECTION HALF SINE WAVE/CURRENT LOADING
5030 Z 5 2
10370 Z 10 2
30537 Z 15 2
* X AND Z DIRECTION WAVE/CURRENT LOADING
5030 X 5 3
5030 Z 5 3
10370 X 10 3
10370 Z 10 3
30537 X 15 3
30537 Z 15 3
A relief valve at node 565 is being investigated for several different reactor decompression conditions. The maximum load
for the first condition is 320 kips in the X direction. This is a ramped time waveform. The valve opens and closes in 5
milliseconds. The duration for the first decompression condition is 50 milliseconds. The maximum load for the second
decompression condition is 150 kips in the X direction. This also is a ramped time waveform. The valve opens and closes in
5 milliseconds and the duration for the second decompression condition is 4 seconds. The third decompression condition
maximum load is 50 kips, and has the same time waveform as the second condition. (It is this decompression state that is
expected to be the most frequent.)
There must be two shock tables defined, one for the 50 ms duration waveform, and one for the 4 second duration waveform.
Chapter 5 Controlling the Dynamic Solution 5-33
Three different maximum force patterns are defined:
* REACTOR DECOMP CONDITION 1
320000 X 565 1
* REACTOR DECOMP CONDITION 2
150000 X 565 2
* REACTOR DECOMP CONDITION 3 (MOST FREQUENT)
50000 X 565 3
A startup shock wave passes through a single elbow system. Nodes in the piping model are 5, 10, and 15. The system is
shown as follows:
As the wave starts off between 5 and 10 there is an initial dynamic axial load on the anchor at 5. When the shock wave hits
the elbow at 10, the axial load in the 5-10 element balances the initial imbalance at node 5, and there becomes an axial
imbalance in the 10-15 element. This shock load will be modeled as two completely separate impacts on the piping system
The first is the dynamic anchor load at 5. (If 5 is a flexible anchor then this load may cause dynamic displacements of the
piping system and 5 will just be subject to the dynamic time history pulse due to the shock.) Assume the anchor at 5 is a
flexible vessel nozzle. The second shock load is the unbalanced dynamic pressure load in the 10-15 element that exists until
the shock reaches the node 15. Friction in the line resisting movement of the shock wave is considerable. In the time the
wave leaves the anchor at 5 until it encounters the bend at 10 there is a 50% drop in the pulse strength as shown in the
following plot.
5-34 Controlling the Dynamic Solution
This pressure drop was computed using a transient fluid simulator. Between node 10 and node 15 the pulse strength drops
even further as shown as follows.
The Force Spectrum input for this loading is as shown as follows:
* X DIRECTION LOAD ON FLEXIBLE ANCHOR AT 5
-5600 X 5 1
* Z DIRECTION LOAD ON ELBOW AT 10
2800 Z 10 2
Chapter 5 Controlling the Dynamic Solution 5-35
Lumped Masses
Lumped Masses
Mass
Enter the concentrated mass in the units shown, a positive concentrated mass is added to the mass at the node. A negative
concentrated mass is subtracted from the mass at the node and a zero entry deletes all mass for the node.
Direction
Can be X, Y, Z, or ALL. ALL can be abbreviated A. If X, Y, or Z is entered, then the mass is only added or subtracted for
that direction.
Start Node
Node where the mass is to act. This entry is required. If entered without a stop node and increment, then this node must
exist in the piping system. If entered with a stop node and increment then the range of nodes identified by the loop must
include at least one node in the piping system. See the examples that follow.
5-36 Controlling the Dynamic Solution
Stop Node
Used as part of a range of nodes lumped mass command. See the examples that follow. This entry is optional.
Increment
Used as part of a range of nodes lumped mass command. See the examples that follow. This entry is optional.
There can be any number of line entries in the lumped mass data.
The zero mass capability with the range of nodes entry is particularly useful when the user has a part of the system for
which he is not interested in the modes. That part of the system would have been modeled for its stiffness effect only. One
example is structural steel models. It is not uncommon for a user to delete all of the mass for nodes in the structural steel
model. (Steel models are often only entered to include their stiffness effects and so the omission of their dynamic effects is
often not significant.)
EXAMPLES:
450 ALL 40
Note: The node range loop starts from node 12, which is not defined and goes through node 25 in steps of 1. Some nodes
dont exist in this range but this is not an error as long as at least one node in the range defined by 12 through 25 by 1, exists
in the system.
0.0 ALL 12 25 1
375 A 25 50 5
0.0 X 1 600 1
0.0 Y 1 600 1
Chapter 5 Controlling the Dynamic Solution 5-37
Snubbers
Snubbers
Stiffness
Enter the stiffness for the snubber in the units shown. If the snubber is rigid enter a value of 1.0E12. The stiffness of the
snubber must be given and must be positive.
Direction
Enter the line of action of the snubber as either X, Y, Z, or as direction cosines or direction vectors. The format for direction
cosines is (cx,cy,cz), and for direction vectors is (vx, vy, vz). See the example that follows for the entry of some typical
skewed snubbers.
Node
Enter the node where the snubber acts. This is a required entry. If the snubber acts between the piping system and a fixed
point in space, then leave the CNode field blank. Connecting Nodes work for snubbers just like they do for restraints.
5-38 Controlling the Dynamic Solution
CNode
If the snubber acts between one point on the piping system and another point on the piping system, then enter the node that
the snubber connects to.
EXAMPLES:
1 Add rigid snubber at node 150 in the Z direction.
1E12 Z 150
2 Add rigid snubbers at nodes 160, 165, and 170 in the Z direction.
1E12 Z 160
1E12 Z 165
1E12 Z 170
3 Add a rigid snubber between the structural steel node 1005 and the piping node 405 in the Z direction.
1E12 Z 405 1005
4 Add a 5,000 lb./in. snubber in the X and Y directions at the piping node 500. The X snubber should connect to the
structural steel node 1050 and the Y snubber should connect to the overhead line at node 743.
HORIZONTAL SNUBBER BETWEEN STEAM LINE AND STEEL 5000 X 500 1050.
VERTICAL SNUBBER BETWEEN STEAM LINE AND OVER HEAD COOLING WATER LINE
5000 Y 500 743
Chapter 5 Controlling the Dynamic Solution 5-39
Dynamic Control Parameters
Control Parameters
The type of analysis chosen by the user in the Dynamic Input Processor determines the active Control Parameters.
CAESAR II will only display this list of active Control Parameters. In addition, the calculation details can be fine-tuned using
many of the other Control Parameters, maximizing accuracy of results for most dynamic problems. The impact and use of
these parameters, as well as their technical bases, are described in this section.
The list of the control parameters, along with the Analysis Types for which they are active, displays in the table on the
following page.
5-40 Controlling the Dynamic Solution
Notes:
X-required
1 If system has nonlinear restraints or hanger design
2 If any restraints have friction
3 Either "Max. No. of Eigenvalues" or "Frequency Cutoff" required
4 If modal combination method is GROUP or 10%
5 If modal combination method is DSRSS
6 If USNRC Regulatory Guide 1.60 or Uniform Building Code seismic spectra are used
7 If independent support movement (USM) loads are present
8 If pseudo-static components are inducted
9 If missing mass components are included
10 If multiple spectrum loads are applied in the same direction
Analysis Type (Harmonic/Spectrum/Modes/Time-History)
The first parameter is used to select from the available dynamic analysis types, which are Harmonic (direct solution),
Response Spectrum (any combination of seismic, anchor movement, and force loadings), Modal Extraction, Range, and
Time History (linear modal). These analysis types are described below:
Chapter 5 Controlling the Dynamic Solution 5-41
Harmonic Analysis
Generally, the response of a system to a dynamically applied load is expressed through the dynamic equation of motion:
Where:
M = system mass matrix
= acceleration vector, as a function of time
C = system damping matrix
= velocity vector, as a function of time
K = system stiffness matrix
x(t) = displacement vector, as a function of time
F(t) = applied load vector, as a function of time
Unfortunately, this differential equation cannot be solved explicitly, except in a few specific cases. Harmonic analysis looks
at one of these casesthe set of dynamic problems where the forces or displacements (i.e., pulsation or vibration) acting on
the piping system take sinusoidal forms. Under harmonic loading, when damping is zero, the dynamic equation of the
system can be reduced to
M (t) + K x(t) = F
0
cos (e t + Q)
Where:
F
0
= harmonic load vector
e = angular forcing frequency of harmonic load (radian/sec)
t = time
Q = phase angle (radians)
This differential equation can be solved directly, yielding the nodal displacements at any time (and from there the system
reactions, forces and moments, and stresses).
The equation has a solution of the form
x (t) = A cos (e t + Q)
Where:
A = vector of maximum harmonic displacements of system
Since acceleration is the second derivative of displacement with respect to time,
(t) = -A e
2
cos e t
Inserting these equations for displacement and acceleration back into the basic harmonic equation of motion yields,
-M A e
2
cos (e t + Q) + K A cos (e t + Q) = F
o
cos (e t + Q)
Dividing both sides of this equation by cos (e t + Q),
-M A e
2
+ K A = F
o
5-42 Controlling the Dynamic Solution
Reordering this equation,
(K - M e
2
) A = F
o
This is exactly the same form of the equation as is solved for all linear (static) piping problems. The appealing thing about
this is that the solution time for each excitation frequency takes only as long as a single static solution, and, when there is no
phase relationship to the loading, the results give the maximum dynamic responses directly. Due to the speed of the
analysis, and because the solutions are so directly applicable, it is advisable to make as much use of this capability as
possible. Two considerations must be kept in mind:
When damping is not zero, the harmonic equation can only be solved if the damping matrix can be defined as the sum
of multiples of the mass and stiffness matrix (Rayleigh damping), i.e.:
[C] = a [M] + b [K]
On a modal basis, the relationship between the ratio of critical damping Cc and the constants a and b is given as
2 2
Cc
o |e | |
= +
|
e
\ .
Where:
e = Undamped natural frequency of mode (rad/sec)
For practical problems, o is extremely small, and so may be ignored. Therefore the definition of | reduces to
| = 2 Cc/e
CAESAR II uses this implementation of damping for its harmonic analysis; however there are still two problems. First, for
multi-degree-of-freedom systems, there is not really a single b, but there must be only a single b in order to get a solution of
the harmonic equation. The second problem is that the modal frequencies are not known prior to generation of the damping
matrix. Therefore the w used in the calculation of b is the forcing frequency of the load, instead of the natural frequency of a
mode. When the forcing frequency of the load is in the vicinity of a modal frequency, this gives a good estimation of the
true damping.
If multiple harmonic loads occur simultaneously, and they are not in phase, system response is the sum of the responses
due to the individual loads:
x(t) = S A
i
cos (e t + Q
i
)
Where:
A
i
= displacement vector of system under load i
Q
i
= phase angle of load i
In this case, an absolute maximum solution cannot be found. Rather, solutions for each load, and the sum of these, must be
found at various times in the load cycle. These combinations should then be reviewed in order to determine which one
causes the worst load case. Alternatively, CAESAR II can select the frequency/phase pairs which maximize the system
displacement.
Note: Damped harmonics will always cause a phased response.
The biggest use by far of the harmonic solver is in analyzing low frequency field vibrations resulting from either fluid
pulsation or out-of-round rotating equipment displacements. The approach typically taken towards solving this type of
problem is described briefly below:
1 A potential dynamic problem is first identified in the fieldeither in terms of large cyclic vibrations or high stresses
(fatigue failure) being present in an existing piping system, raising questions of whether this represents a dangerous
Chapter 5 Controlling the Dynamic Solution 5-43
situation. As many symptoms of the problem (quantifiable displacements, overstress points, etc.) are identified as
possible, for future use in refining the dynamic model.
2 A model of the piping system is built using CAESAR II. This should be done as accurately as possible, since system, as
well as load, characteristics affect the magnitude of the developed response. Particular attention should be paid when
modeling the area where the vibration occurs. This might include accurately representing valve operators, flange pairs,
orifice plates and other in-line equipment. It may also be a good idea to add additional nodes in the area of the vibration.
3 The engineer next postulates the cause of the load, and from that, an estimate of the frequency, magnitude, point, and
direction of the load. This is somewhat difficult because the dynamic loads can come from many sources. Dynamic
loads may be due to internal pressure pulses, external vibration, flow shedding at intersections, two phase flow, etc., but
in almost all cases, there is some frequency content of the excitation that corresponds to (and therefore excites) a system
mechanical natural frequency. If the load is caused by equipment, then the forcing frequency is probably some multiple
of the operating frequency; if the load is due to acoustic flow problems, then the forcing frequency can be estimated
through the use of Strouhals equations (from fluid dynamics). Using the best assumptions available, the user should
estimate the magnitudes and points of application of the dynamic load.
4 The loading is then modeled using harmonic forces or displacements (normally depending upon whether the cause is
assumed to be pulsation or vibration) and several harmonic analyses are done, sweeping the frequencies through a
range centered about the target frequency (in order to account for uncertainty). The results of each of the analyses are
examined for signs of large displacements, indicating harmonic resonance. If the resonance is present, the results of the
analysis are compared to the known symptoms from the field. If they are not similar (or if there is no resonance), this
indicates that the dynamic model is not a good one, so it must be improved, either in terms of a more accurate system
(static) model, a better estimate of the load, or a finer sweep through the frequency range. Once the model has been
refined, this step is repeated until the mathematical model behaves just like the actual piping system in the field.
5 At this time, there is a good model of the piping system and a good model of the loads (or, more accurately, a good
model of the relationship of the load characteristics to the system characteristics). The results of this run are evaluated
in order to determine whether they indicate a problem. Since harmonic stresses are cyclic, they should be evaluated
against the endurance limit of the piping material; displacements should be reviewed against interference limits or
esthetic guidelines.
6 If the situation is deemed to be a problem, its cause must be identified, where the cause is normally the excitation of a
single mode of vibration. For example, the Dynamic Load Factor for a single damped mode of vibration, with a
harmonic load applied is
2
2 2
1 (2 )
[1 ( ) ] (2 )
c f m
f m c f m
C
DLF
C
+ e e
=
e e + e e
Where:
DLF = dynamic loading factor
C
c
= ratio of system damping to critical damping,
where critical damping =
e
f
= forcing frequency of applied harmonic load
e
n
= natural frequency of mode of vibration
A modal extraction of the system is done; one (or more) of these modes should have a natural frequency close to the forcing
frequency of the applied load. The guilty mode can be further identified as that one having a shape very similar to the shape
of the total system vibration, since this mode shape has certainly been dynamically magnified far beyond the other modes
(and thus predominates in the final vibrated shape).
7. Once the guilty mode has been identified, it must be eliminated. This is done most easily by adding a restraint at a high
point (and in the direction thereof) of the mode shape. If this cannot be done, the mode may also be altered by changing the
mass distribution of the system. If no modification of the system is possible, it may be possible to alter the forcing
frequency of the load. If the dynamic load was postulated to be due to internal acoustics, it is recommended that the pipe not
5-44 Controlling the Dynamic Solution
be rerouted at this point, as rerouting the pipe will change the internal flow conditions (which may resolve or amplify the
problem, but in either case will void CAESAR IIs good model of the system). After modifying the system, the harmonic
problem (using the single forcing frequency determined as a good model) is then re-run, and the stresses, displacements,
etc. are re-evaluated.
8. If the dynamic problem has been adequately solved, the system is now re-analyzed statically to determine the effects of
any modifications on the static loading cases. (Remember, adding restraint normally increases expansion stresses, while
adding mass increases sustained stresses.)
The user may process output from a harmonic analysis in two ways:
Use of the output processor to review displacement, restraint, force, or stress data either graphically or in report form.
Animation of the displacement pattern for each of the frequency load cases.
Note: The results of harmonic dynamic loads cannot be combined using the Static/Dynamic Combination option.
Spectrum Analysis
A spectrum analysis represents an attempt to estimate the maximum response developed in a system during a transient load.
The results are a statistical summation of the maximum displacements, forces, reactions, stresses, etc; the individual
responses do not represent an actual physical loading case in that the maxima may all occur at different times. Spectrum
analyses are especially useful when the loading profile is random, or otherwise not known exactly, such as with seismic
loads. CAESAR II provides the ability to perform two types of spectrum analyses (which may be combined): for seismic and
force loadings. Seismic loadings may be evaluated either uniformly over the entire system, or applied through individual
support groups (with corresponding anchor movements). Force spectra analyses may be used to analyze impulse loadings,
such as those due to relief valve, fluid hammer, or slug flow. These two types are described in the following paragraphs.
Seismic Spectrum Analysis. Seismic loads cannot be solved through time history analyses, since earthquakes cause random
motion, which may be different for each earthquake, even those occurring at the same site. To simplify the analytical
definition of the earthquake, it is necessary to get the expected random waveform of acceleration (or velocity or
displacement) vs. time into some simple frequency-content plot. The most predominantly used frequency-content plot is the
response spectrum. A response spectrum for an earthquake load can be developed by placing a series of single degree-of-
freedom oscillators on a mechanical shake table and feeding a typical (typical for a specific site) earthquake time history
through it, measuring the maximum response (displacement, velocity, or acceleration) of each oscillator.
Chapter 5 Controlling the Dynamic Solution 5-45
The expectation is that even though all earthquakes are different, similar ones should produce the same maximum
responses, even though the time at which they occur will differ with each individual occurrence. (Responses will be based
on the maximum ground displacement and acceleration, the dynamic load factors determined by the ratios of the pre-
dominant harmonic frequencies of the earthquake to the natural frequencies of the oscillators, and system damping.)
Response spectra for a number of damping values can be generated by plotting the maximum response for each oscillator. A
plot of a set of typical response spectra is shown in the following figure.
Seismic response spectra resemble harmonic Dynamic Load Factor curves, since seismic loads evidence strong harmonic
tendencies. As damping value increases, the system response approaches the ground motion. Seismic spectra usually also
show strong evidence of flexible, resonant, and rigid areas. Spectra may have multiple peaks due to filtering by the building
and/or piping system; however multiple peaks are usually enveloped in order to account for uncertainties in the analysis.
Seismic response spectra peaks are typically spread to account for inaccuracies as well.
The idea behind the generation of the response spectra is that a systems modes of vibration will respond to the load in the
exact same manner as will a single degree-of-freedom oscillator. System response may be plotted in terms of displacement,
velocity, or acceleration, since these terms of the spectra are all related by the frequency:
d = v / e = a / e
2
Where:
d = displacement from response spectrum at frequency
v = velocity from response spectrum at frequency
e = angular frequency at which response spectrum parameters are taken
a = acceleration from response spectrum at frequency
Response Spectrum analysis proceeds according to the following steps:
1 Modes of vibration are extracted from the system using an Eigensolver algorithm. Each mode has a characteristic
frequency and mode shape.
2 The maximum response of each mode under the applied load is determined from the spectrum value corresponding to
the modes natural frequency.
3 The total system response is determined by summing the individual modal responses, using methods that reflect the
time independence of the responses and the portion of system mass allocated to each mode.
There are four major sources of earthquake spectra available to the CAESAR II user:
5-46 Controlling the Dynamic Solution
Predefined El Centro (available in the CAESAR II databasespectrum name = ELCENTRO): This data is taken from J.
Biggs Introduction to Structural Dynamics and is based on the north-south component of the May 18, 1940 El
Centro California earthquake. The recorded maximum acceleration was 0.33 g. The spectrum provided here is intended
to apply to elastic systems having 5 to 10 percent critical damping.
Predefined Nuclear Regulatory Guide 1.60 (Available in the CAESAR II database): The predefined spectrum names are:
1.60H.5 1.60V.5-- Horizontal/vertical,0.5% damping
1.60H2 1.60V2 -- Horizontal/vertical,2.0% damping
1.60H5 1.60V5 -- Horizontal/vertical,5.0% damping
1.60H7 1.60V7 -- Horizontal/vertical,7.0% damping
1.60H10 1.60V10 -- Horizontal/vertical,10.0% damping
These spectra are constructed according to the instructions given in Regulatory Guide 1.60 for seismic design of nuclear
plants. They must also be scaled up or down by the maximum ground acceleration (ZPAzero period acceleration), which
can be specified in the CAESAR II control parameter spreadsheet.
Predefined Uniform Building Code (Available in the CAESAR II database). The predefined spectrum names are:
UBCSOIL1 Spectrum for rock and stiff soils
UBCSOIL2 Spectrum for deep cohesionless or stiff clay soils
UBCSOIL3 Spectrum for soft to medium clays and sands
These spectra represent the normalized response spectra shapes (for three soil types) provided in Figure 23-3 of the Uniform
Building Code (1991 Edition). When used, they must be scaled by the ZPA, which is the product of Z and I (Where Z is the
seismic zone coefficient and I is the earthquake importance factor, from UBC Tables 23-I and 23-L, respectively). The ZPA
can be specific using the CAESAR II control parameter spreadsheet.
User defined spectra: User defined spectra may be entered with period or frequency as the range, and displacement,
velocity, or acceleration as the ordinate. These spectra may be read in from a text file or entered directly into a spectrum
table during dynamic input processing.
Independent Support Motion Applications. Earthquake ground motions are caused by the passing of acoustic shock
waves through the earths soil. These waves are usually hundreds of feet long. If supports having foundations in the soil are
grouped together within a several hundred foot radius of each other they will typically see exactly the same excitation from
the earthquake. If all of the supports for a particular piping system are attached directly to ground type supports, each
support will be excited by an essentially identical time waveform. This type of excitation is known as uniform support
excitation. Often pipe is supported from rack, building, or vessel structures as well as from ground type supports. These
intermediate structures serve to, in some cases, filter and in some cases accentuate the effect of the earthquake. In this
situation, the supports attached to the intermediate structure are not exposed to the same excitation as those that are attached
directly to ground foundations. To accurately model these systems different shocks must be applied to different parts of the
piping system. This type of excitation is known as independent support motion (ISM) excitation. While the different support
groups are exposed to different shocks, there are also relative movements between support groups that dont exist for
uniform support excitation. The movement of one support group relative to another is termed pseudostatic displacement, or
seismic anchor movements. For uniform support excitation there are spatial and modal response components available for
combination. For independent support excitation there are spatial and modal response components available for each
different support group, plus pseudostatic components of the earthquake that must be added into the dynamic response as
well.
The major difference when running ISM type earthquake loads comes while building the shock load cases. Whereas in the
uniform excitation case the shock acts implicitly over all of the supports in the system, in the ISM case different shocks act
on different groups of supports. The shock load case input form appears:
SHOCK NAME FACTOR DIR START NODE STOP NODE INCR ANCHOR
MVMT
Name, Factor, and Direction are all that is entered for uniform support excitations. For ISM type shocks, the group of nodes
over which the shock acts must be specified as well, using the Start Node, Stop Node, and Increment entries. The Anchor
Movement entry is used to explicitly define the seismic displacement of the restraint set. This displacement is used to
Chapter 5 Controlling the Dynamic Solution 5-47
calculate the pseudostatic load components. If omitted, the program defaults to the displacement derived from the response
spectrum entry corresponding to the lowest frequency.
Force Spectrum Analysis. A similar method can be followed for non-random loads, such as an impulse load for which the
force vs. time profile is known. A look at the equation for the earthquake problem explains why the force spectrum solution
is very similar to the earthquake solution:
The term on the right hand side is nothing more than a dynamic force acting on the piping system, i.e. F = Ma, so the
analogous equation to be solved for the force spectrum problem is:
Where:
F = the dynamic load (water hammer or relief valve)
Instead of the displacement, velocity, or acceleration spectrum used for the seismic problem, a Dynamic Load Factor
spectrum is used for a force spectrum problem. A DLF spectrum gives the ratio of the maximum dynamic displacement
divided by the maximum static displacement. Whereas the earthquake response spectrum analysis method started with the
time history of an earthquake excitation, the force spectrum analysis method is done in exactly the same wayexcept that
the analysis starts with the force vs. time profile. Just as for the earthquake, this time history loading can be applied to a
shake table of single degree-of-freedom bodies, with a response spectrum (in this case, DLF vs. natural frequency) being
generated by dividing the maximum oscillator displacements by the static displacements expected under the same load. An
alternate means of generating a response spectrum for an impulse load is to numerically integrate the dynamic equation of
motion for oscillators of various frequencies under the applied load. This can be done using the Pulse Table/DLF
Spectrum Generator available from the CAESAR II Main Dynamics Menu.
The user may process output from a spectrum analysis in two ways:
Use of the output processor to review the natural frequencies, mode shapes, participation factors, included mass/force,
displacements, and restraint loads, forces, or stresses in report form. Dynamic results also show the largest modal
contributor, along with the mode and shock load responsible for that contribution.
Animation of the individual mode shapes extracted for the spectrum analysis.
Modal Extraction. A modal extraction performs only an Eigensolution (an eigensolution is also performed as the initial
step of the spectrum or modal time history analyses). The Eigensolution algorithm uses an iterative method to solve for
natural frequencies and mode shapes of a piping or structural system. Each mode of the piping system is associated with a
shape and a frequency, which together define the systems tendency to vibrate; the mode shape defining the shape the
system would like to take when it vibrates, and the natural frequency defining the desired speed of the vibration. The
eigensolver returns a set of these for each mode, with the dimensionless mode shape called an eigenvector, and the
frequency returned as the square of the angular frequency ( e
2
), known as the eigenvalue. Given the eigenvalue, the modal
frequency can be expressed in angular frequency (radians per second), cyclic frequency (Hz), or period (seconds per cycle):
eigenvalue = e
2
(radians squared per second squared)
angular frequency = e (radians per second)
cyclic frequency = e / 2t (Hz, or cycles per second)
period = 2t / e (seconds per cycle)
The absolute magnitude of a mode shape displacement computed by an eigensolver is unknown, with only the shape being
given (i.e. only the ratios of the displacements at various degrees of freedom are known for each mode, with these ratios
being constant for each mode). One eigenpair can potentially be calculated for each degree of freedom in the model that
contains some nonzero mass (node point) and some non-rigid stiffness (i.e., is not fully restrained). CAESAR II omits
5-48 Controlling the Dynamic Solution
rotational degrees of freedom from dynamic models in order to simplify the calculationthis is usually acceptable since
rotational modes of vibration usually have very high frequencies, and correspondingly very low mode participation factors.
The user may process output from a modal analysis in two ways:
Use of the output processor to review the natural frequencies and mode shapes in report form.
Animation of the individual mode shapes.
Time History
Time history analysis is a more accurate, more computationally intensive analytical method than is response spectrum
analysis, and is best suited to impulse loadings or other transient loadings where the profile is known. This method of
analysis involves the actual solution of the dynamic equation of motion throughout the duration of the applied load and
subsequent system vibration, providing a true simulation of the system response at all times.
As noted previously, the dynamic equation of motion for a system is
( ) ( ) ( ) ( ) Mx t Cx t Kx t F t + + = && &&
This differential equation cannot be solved explicitly, but may be integrated using numeric techniques by slicing the
duration of the load into many small time steps. Based on an assumption of the behavior of the system between time slices
(i.e., that the change in acceleration between time slices is linear), the system accelerations, velocities, displacements, and
correspondingly, the reactions, internal forces, and stresses can be calculated at successive time steps.
Since the total response of a system is equivalent to the sum of the responses of its individual modes of vibration, the above
equation can be simplified (assuming the damping matrix C is orthogonal), using the transformation x = FX, to be expressed
in modal coordinates:
1
( ) ( ) h ( ) i ( ) x t C x t x t F t ' + + = && &&
Where:
x(t) &&
= acceleration vector (in modal coordinates), as a function of time
C = diagonal damping matrix, where entry C
i
= e
i
c
i
e
i
= angular frequency of mode i
c
i
= ratio of damping to critical damping for mode i
(t) = velocity vector (in modal coordinates), as a function of time
x(t) = displacement vector (in modal coordinates), as a function of time
O = diagonal stiffness matrix, where entry O
i
= e
i
2
This transformation represents N (where N is the number of modes of vibration extracted) uncoupled second order
differential equations, which can then be integrated and summed (using the in-phase, algebraic summation method) to give
the total system response. The CAESAR II program uses the Wilson u method (an extension of the Newmark method) to
integrate the equations of motion, which provides an unconditionally stable algorithm, regardless of time step size chosen.
Only one dynamic load may be defined for a time history analysis (this dynamic load case may be used in as many
static/dynamic combination load case as necessary). However, the single load case may consist of multiple force profiles
applied to the system simultaneously, or sequentially. Each force vs. time profile is entered as a spectrum with an ordinate
of FORCE (in current units) and a range of TIME (in milliseconds). The profiles are defined by entering the time and force
coordinates of the corner points defining the profile. (Note that a time can only be entered once, and that times with zero
force outside of the defined profile need not be entered explicitly.)
Chapter 5 Controlling the Dynamic Solution 5-49
For example, the profiles shown in the following figure are entered as:
TIME (MS) FORCE TIME (MS) FORCE
0.0 0.0 20.0 1000.0
10.0 300.0 60.0 1000.0
20.0 1000.0 30.0 0.0
The load profiles must then be linked with force sets (indicating magnitude, direction, and location of the applied load) in
the shock case. The magnitude of the applied load is determined by the product of the profile force, the force set magnitude,
and the scale in the shock case.
Currently only forces, not moments or restraint displacements, may be entered in the time history load profile. However,
moments can be modeled using force couples, and restraint displacements can be simulated by entering forces equal to the
desired displacement times the restraint stiffness in the direction of the displacement).
The user may process output from a Time History analysis in three ways:
1 Use of the output processor to review the natural frequencies, mode shapes, participation factors, included mass/force,
displacements, and restraint loads, forces, or stresses in report form. CAESAR IIs implementation of time history
analysis provides two types of resultsone results case containing the maximum individual components (axial stress,
X-displacement, MZ reaction, etc.) of the system response, along with the time at which it occurred, and several (the
actual number is determined by user request) results cases representing the actual system response at specific times.
Dynamic results also show the largest modal contributor, along with the mode and transient load responsible for that
contribution.
2 Animation of the shock displacement for the transient load cases. During animation, the displacements, forces,
moments, stresses, and other data associated with individual elements may be displayed at every time step and for the
dynamic load alone, or for any of the static/dynamic combinations.
3 Animation of the individual mode shapes included in the time history response.
Static Load Case for Nonlinear Restraint Status
(Active for: Harmonic, Spectrum, Modal, Range, and Time History)
Currently all of CAESAR IIs dynamic analyses act only on linear systems, so any non-linearities must be linearized prior to
analysis. This means that one-directional restraints will not lift off and reseat, gaps will not open and close, and friction will
not act as a constant effort force. Therefore, for dynamic analyses, all non-linear effects must be modeled as linearfor
example, a one-directional restraint must be modeled as either seated (active) or lifted off (inactive), and a gap must be
5-50 Controlling the Dynamic Solution
either open (inactive) or closed (active). This process is automated when the static load case is selected hereCAESAR II
automatically activates the non-linear restraints in the system to correspond to their status in the selected load case (the user
may think of this as being the loading conditionfor example Operatingof the system at the time at which the dynamic
load occurs). It must be noted that this automated linearization does not always provide an appropriate dynamic model, and
it may be necessary to select other static load cases or even to manually alter the restraint condition in order to simulate the
correct dynamic response.
A static load case must precede the dynamics job whenever one or more of the following situations occur:
There are spring hangers to be designed in the job. The static runs must be made in order to determine the spring rate to
be used in the dynamic model.
There are non-linear restraints, such as one-directional restraints, large-rotation rods, bi-linear restraints, gaps, etc. in
the system. The static analysis must be made in order to determine the active status of each of the restraints for
linearization of the dynamic model.
There are frictional restraints in the job, i.e. any restraints with a nonzero j (mu) value.
The most common arrangement of static loads during typical CAESAR II analyses displays below:
Example 1analyses containing no hanger design:
1 = W+P1+D1+T1+F1 (OPE)
2 = W+P1+F1 (SUS)
3 = L1-L2 (EXP)
In this case, if the operating condition is most likely to exist throughout the duration of the dynamic transient, the correct
entry for this parameter is 1. If the installed condition is more likely to exist during the transient, the entry for this parameter
should be 2. It is extremely unlikely that the expansion case (3) would be correct here, since it does not represent the system
status at any given time, but rather represents the difference between the first two cases.
Example 2analyses containing hanger design:
1 = W+P1+F1 (For hanger design)
2 = W+P1+D1+T1+F1 (For hanger design)
3 = W+P1+D1+T1+F1 (OPE)
4 = W+P1+F1 (SUS)
5 = L3-L4 (EXP)
In this case, the correct static load cases to use are those in which the selected spring hangers have been included; if the
operating condition is the correct load case, the entry for this parameter should be 3. For the installed condition, an entry of
4 is correct.
Stiffness Factor for Friction (0.0 - Not Used)
(Active for: Harmonic, Spectrum, Modal, Range, and Time History)
As noted above, all of CAESAR IIs dynamic analyses are currently linear, so non-linear effects must be linearized. Modeling
of friction in dynamic models presents a special case, since friction actually impacts the dynamic response in two ways
static friction (prior to breakaway) affects the stiffness of the system, by providing additional restraint, while kinetic friction
(subsequent to breakaway) actually affects the damping component of dynamic response; due to mathematical constraints,
damping is ignored for all analyses except time history and harmonics (for which it is only considered on a system-wide
basis).
CAESAR II allows friction to be taken into account through the use of this Friction Stiffness Factor. CAESAR II approximates
the restraining effect of friction on the pipe by including stiffnesses transverse to the direction of the restraint at which
friction was specified. The stiffness of these frictional restraints is computed as:
Chapter 5 Controlling the Dynamic Solution 5-51
K
friction
= (F) (W) (Fact)
Where:
K
friction
= stiffness of frictional restraint inserted by CAESAR II
F = the force at the restraint taken from the static solution
W = mu, friction coefficient at restraint, as defined in the static model
Fact = Friction Factor from the control spreadsheet
This factor should be adjusted as necessary in order to make the dynamic model simulate the systems actual dynamic
response (note that use of this factor does not correspond to any actual dynamic parameter, but is actually a tweak factor
to modify system stiffness). Entering a friction factor greater than zero causes these friction stiffnesses to be inserted into
the dynamics job. Increasing this factor correspondingly increases the effect of the friction. Entering a friction factor equal
to zero ignores any frictional effect in the dynamics job.
Max. No. of Eigenvalues Calculated (0-Not used)
(Active for: Spectrum, Modal, and Time History)
The first stage of the Spectrum, Modal, and Time History analyses, is the use of the Eigensolver algorithm to extract the
piping systems natural frequencies and mode shapes. For the Spectrum and Time History analyses, the response under
loading is calculated for each of the modes, with the system response being the sum of the individual modal responses.
Obviously, the more modes that are extracted, the more the sum of those modal responses resembles the actual system
response. The problem is that this algorithm uses an iterative method for finding successive modes, so extraction of a large
number of modes usually requires much more time than does a static solution of the same piping system. The object is to
extract sufficient modes to get a suitable solution, without straining computational resources.
CAESAR II permits the user to specifyeither through a mode number cutoff or a frequency cutoffthe number of modal
responses to be included in the system results. This parameter is used, in combination with the Frequency Cutoff described
below, to limit the maximum number of modes of vibration to be extracted during the dynamic analysis. If this parameter is
entered as 0, the number of modes extracted is limited only by the frequency cutoff (and potentially, the number of degrees-
of-freedom in the system model).
If the analyst is more interested in providing an accurate representation of the system displacements, it may only be
necessary to request the extraction of a few modes, allowing a rapid calculation time. However, if an accurate estimate of
the forces, stresses, etc. in the system is the objective, calculation time grows as it becomes necessary to extract far more
modes. This is particularly true in the case when solving a fluid hammer problem in the presence of axial restraints; often
modes with natural frequencies of up to 300 Hz can be large contributors to the solution.
The usual procedure for determining how many modes are sufficient is to extract a certain number of modes and review the
results; then to repeat the analysis while extracting 5 to 10 additional modes, and comparing the new results to the old. If
there is a significant change between the results, a new analysis is made, again extracting 5 to 10 more modes above those
that were extracted for the second analysis. This iterative process continues until the results taper off, becoming asymptotic.
This procedure has two drawbacks, the first one obviousthe time involved in making the multiple analyses, as well as the
time involved in extracting the potentially large number of modes. The second drawback, occurring with Spectrum analysis,
is less obviousa degree of conservatism is introduced when combining the contributions of the higher order modes.
Possible spectral mode summation methods include SRSS, ABSOLUTE, and GROUPall methods that combine modal
results as same-sign (positive) values. In reality, theory states that the rigid modes actually act in phase with each other, and
should therefore be combined algebraically, thus permitting the response of some rigid modes to cancel the effect of other
rigid modes (this is actually what occurs in a time history analysis). Because of this conservatism, it is actually possible to
get results which exceed twice the applied load, despite the fact that the Dynamic Load Factor (DLF) of an impulse load
cannot be greater than 2.0.
5-52 Controlling the Dynamic Solution
An alternative method of ensuring that sufficient modes are considered in the dynamic model is through the use of the
Included Mass Data Report. This report (available from the Dynamic Output Screen) is compiled for all spectrum and time
history shock cases, whether missing mass (see description in the section Include Missing Mass Components) is to be
included or not. It displays the percent of system mass along each of the three global axes, as well as the percent of total
force, which has been captured by the extracted modes.
The percent of system mass active along each of the three global axes (X-, Y-, and Z-) is calculated by summing the modal
mass (corresponding to the appropriate directional degree-of-freedom) attributed to the extracted modes and dividing that
sum by the sum of the system mass acting in the same direction:
% Active Mass
x
[ ]
[ ]
100( )
e
M i
M i
=
Summed over i = 1 to n, by 6
(X-direction degrees of freedom)
%Active Mass
Y
[ ]
[ ]
100( )
e
M i
M i
=
Summed over 1 = 2 to n, by 6
(Y-direction degrees of freedom)
%Active Mass
z
[ ]
[ ]
100( )
e
M i
M i
=
Summed over 1 = 3 to n, by 6
(Z-direction degrees of freedom)
Where:
M
e
= vector (by degree-of-freedom) of sum (over all extracted modes) of effective modal masses
M = vector corresponding to main diagonal of system mass matrix
The maximum possible percent of active mass which is theoretically possible is of course 100%, with 90-95% usually
indicating that a sufficient number of modes have been extracted to provide a good dynamic model.
The percent of active force is calculated by the following factors:
separately summing the components of the effective force acting along each of the three directional degrees-of-freedom
combining them algebraically
doing the same for the applied load
taking the ratio of the effective load divided by the applied load
Chapter 5 Controlling the Dynamic Solution 5-53
For example:
F
e
x
= EF
e
[i]
Fx = EF[i]
Summed over i = 1 to n, by 6
(X - Direction degrees of freedom)
F
e
y
= EF
e
[i]
Fy = EF[i]
Summed over i = 2 to n, by 6
(Y - Direction degrees of freedom)
F
e
z
= EF
e
[i]
Fz = EF[i]
Summed over i = 3 to n, by 6
(Z - Direction degrees of freedom)
% Active Force
2 2 2
2 2 2
[ ]
100*
[ ]
+ +
=
+ +
e e e
F x F y F z
Fx Fy Fz
Where:
F
eX
,F
eY
,F
eZ
= effective force (allocated to extracted modes) acting along the global X-, Y-, and Z-
axes, respectively
F
r
= vector of effective forces (allocated to extracted modes)
F
X
,F
Y
,F
Z
= total system forces acting along the global X-, Y-, and Z-axes, respectively
F = vector of total system forces
The maximum possible percent which is theoretically possible for this value is also 100%; however, in practice it may be
higher, indicating an uneven distribution of the load and mass in the system model. There is nothing inherently wrong with
an analysis where the included force exceeds 100%if the missing mass correction is included, the modal loadings will be
adjusted to conform to the applied loading automatically. Often the percent of included force can be brought back under
100% by extracting a few more modes. At other times, the situation can be remedied by improving the dynamic model
through a finer element mesh, or, more importantly, equalizing the mass point spacing in the vicinity of the load.
Frequency Cutoff (HZ)
(Active for: Spectrum, Modal, and Time History)
As noted above, CAESAR II permits the user to specify either a number of modes or a frequency cutoff for extracting modes
to be considered in the dynamic analysis. Modal extraction ceases when the Eigensolver extracts either the number of
modes requested, or extracts a mode with a frequency above that of the Frequency Cutoff, whichever comes first.
One recommendation for selection of a frequency cutoff point is that the user extract modes up to, but not far beyond, a
recognized rigid frequency, and then include the missing mass correction (discussed in the section Include Missing Mass
Components). Choosing a cutoff frequency to the left of the response spectrums resonant peak will provide a non-
5-54 Controlling the Dynamic Solution
conservative result, since resonant responses may be missed. During spectrum analysis, using a cutoff frequency to the right
of the peak, but still in the resonant range, will yield either over- or under-conservative results, depending upon the method
used to extract the ZPA from the response spectrum. (In the case of time history analysis, selecting a cutoff frequency to the
right of the peak, but still in the resonant range, will probably yield non-conservative results, since the missing mass force is
applied with a dynamic load factor of 1.0). Extracting a large number of rigid modes for calculation of the dynamic
response may be conservative in the case of Spectrum analysis, since all spectral modal combination methods (SRSS,
GROUP, ABS, etc.) give conservative results versus the algebraic combination method (always used during time history
analysis), which gives a more realistic representation of the net response of the rigid modes. Based upon the response
spectrum shown in the following figure, an appropriate cutoff point for the modal extraction would be about 33 Hz.
1 Non-conservative cutoff (Misses amplification of any modes in resonant range)
2 Conservative cutoff (Multiplies missing mass contribution by excessive DLF1.6)
3 Optimal cutoff (Includes all modes in resonant range, uses low DLF1.05for missing mass contribution, minimizes
combination of rigid modes)
4 Conservative Cutoff (Too many rigid modes combined using non-conservative summation methods)
When the analysis type is SPECTRUM, MODES, or TIMEHIST, either this parameter or the previous one must be entered.
Closely Spaced Mode Criteria/Time History Time Step (ms)
(Active for: Spectrum/GROUP and Time History)
This parameter does double duty, depending upon the analysis type. For a Spectrum analysis type with GROUP modal
Combination Method (as defined by USNRC Regulatory Guide 1.92), this parameter specifies the frequency spacing
defining each modal groupi.e., the percent (of the base frequency) between the lowest and highest frequency of the group.
Regulatory Guide 1.92 specifies the group spacing criteria as 10% (entered here as 0.1), so it is unlikely that the user would
ever wish to change the Closely Spaced Mode Criteria from the CAESAR II default value of 0.1. The GROUP modal
combination method is described in detail in the section Modal Combination Method found later in this chapter.
For a Time History analysis type, this parameter is used to enter the length of the time slice, in milliseconds, to be used by
the program during its step-by-step integration of the equations of motion for each of the extracted modes (CAESAR II uses
the unconditionally stable Wilson q integration method, so any size time step will provide a solution, with a smaller step
providing greater accuracyand more strain on computational resources). The time step should be sufficiently small that it
can accurately map the force vs. time load profile (i.e., the time step should be smaller than typical force ramp times).
Additionally, the time step must be small enough that the contribution of the higher order modes is not filtered from the
response. For this reason, it is recommended that the time step should be selected such that Time Step (in seconds) times
Chapter 5 Controlling the Dynamic Solution 5-55
Maximum Modal Frequency (in Hz) be less than 0.1. For example, if the modal frequency cutoff is set to 50 Hz, the time
step should be set to a maximum of 2 milliseconds:
0.002 sec x 50 Hz = 0.1
Load Duration (Time History or DSRSS Method) (Sec.)
(Active for: Spectrum/DSRSS and Time History)
This parameter is used to specify the duration of the applied dynamic load. For a Time History analysis, this parameter is
used to specify the total length of time (in seconds) over which the dynamic response is to be simulated. The load duration,
divided by the time step size (see the previous section) gives the total number of integration steps making up the solution
(currently CAESAR II limits the number of time steps to 5000, or as permitted by available memory and system size). It is
recommended that, if possible, the duration be at least equal to the maximum duration of the applied load, plus the period
(in seconds) of the first extracted mode. This allows simulation of the system response throughout the imposition of the
external load, plus one full cycle of the resulting free vibration. After this point, the response will die out, according to the
damping value used. For example, if the applied load is expected to last 150 milliseconds, and the lowest extracted
frequency is 3Hz, the load duration should be set to a minimum of 0.150 plus 1/3, or 0.483 seconds.
For a Spectrum analysis using the Double Sum (DSRSS) modal Combination Method (as defined by USNRC Regulatory
Guide 1.92), this parameter is used to specify the duration of the earthquake, in seconds. This duration is used to compute
the modal correlation coefficients based on empirical data. The DSRSS modal combination method is described in detail in
the section Modal Combination Method later in this chapter.
Damping (Time History or DSRSS) (Ratio of Critical)
(Active for: Spectrum/DSRSS, Harmonics, and Time History)
This parameter is used to specify the system damping value, as a ratio of critical damping. Typical values for piping
systems, as recommended in USNRC Regulatory Guide 1.61 and ASME Code Case N-411, range from 0.01 to 0.05, based
upon pipe size, earthquake severity, and the systems natural frequencies.
Generally, damping cannot be considered in the mathematical solutions required for spectrum or harmonic analysis. It is
therefore ignored (or solved as specialized cases) in most analyses, and must be instead considered through adjustment of
the applied loads (generation of the response spectrum) and/or system stiffness.
For a Time History analysis, damping is used explicitly, since this method uses a numeric solution to integrate the dynamic
equations of motion.
For a Spectrum analysis using the Double Sum (DSRSS) modal Combination Method (as defined by USNRC Regulatory
Guide 1.92), the damping value is used in the computation of the modal correlation coefficients. (Note that CAESAR II does
not permit the specification of damping values for individual modes.) The DSRSS modal combination method is described
in detail in the section Modal Combination Method later in this chapter.
For a Harmonic analysis, this ratio is converted to Rayleigh Damping, where the damping matrix can be expressed as
multiples of the mass and stiffness matrices:
[C] = a [M] + b [K]
On a modal basis, the relationship between the ratio of critical damping C
c
and the constants a and b is given as:
5-56 Controlling the Dynamic Solution
Where:
e = undamped natural frequency of mode (radians/sec)
For many practical problems, a is extremely small, and so may be ignored, reducing the relationships to:
o = 0 | = 2 C
c
/ e
CAESAR II uses this implementation of damping for its harmonic analysis, with the exception that a single b is calculated for
the multi-degree-of-freedom system, and the w used is that of the load forcing frequency. When the forcing frequency is in
the vicinity of a modal frequency, this gives an accurate estimate of the true damping value.
ZPA (Reg. Guide 1.60/UBC- G's)/# Time History Output Cases
(Active for: Spectrum/1.60/UBC and Time History)
This parameter does double duty, depending upon the analysis type. When used with certain pre-defined normalized
response spectra, it is used as the acceleration factor (in g's) by which the spectrum is scaled. For example, when a
spectrum analysis uses one of the pre-defined spectra names beginning with "1.60" (i.e., 1.60H.5 or 1.60V7), CAESAR II
constructs an earthquake spectrum according to the instructions given in USAEC (now USNRC) Regulatory Guide 1.60.
That guide requires that the shape of the response spectrum be chosen from the curves shown in the following figures, based
upon the system damping value (for example, the .5 or 7 in the spectrum names 1.60H.5 or 1.60V7). If the analysis uses one
of the pre-defined spectra names beginning with "UBC" (i.e., UBCSOIL1), CAESAR II uses the normalized seismic response
spectra for the corresponding soil type from Table 23-3 from the Uniform Building Code (1991 Edition). Both the Reg
Guide 1.60 and the UBC curves are normalized to represent a ground acceleration (ZPA) of lg; the true value is actually site
dependent. Therefore, entering ZPA value here appropriately scales any Regulatory Guide 1.60 or the Uniform Building
Code response spectra.
Chapter 5 Controlling the Dynamic Solution 5-57
When performing Time History analysis, this parameter is used to specify the number of distinct times at which the results
of the load cases (the dynamic load as well as all static/dynamic combinations) should be generated. In addition, CAESAR II
generates one set of results (for each load case) containing the maximum of each output value (displacement, force, stress,
etc.) along with the time at which it occurred. The times for which results are generated are determined by dividing as
evenly as possible the load duration by the number of output timesfor example, if the load duration is 1 second, and 5
output cases are requested, results will be available at 200, 400, 600, 800, and 1000 milliseconds (in addition to the
maximum case). The total number of results cases generated for an analysis is the product of the number of load cases (one
dynamic case plus the number of static/dynamic combination cases) times the number of results cases per load (one maxima
case plus the requested number of output cases). Currently the total number of results cases is 999:
(1 + # Static/Dynamic Combinations) x (1 + # Output Cases) s 999
At least one output case (in addition to the automatically generated maxima case) must be requested; more than one is not
really necessary, since the worst case results are reflected in the Maxima case and individual results at every time step are
available through the ELEMENT command when animating the Time History results.
Re-use Last Eigensolution
(Active for: Spectrum and Time History)
When repeating a dynamic analysis, this parameter may be set to Yes, causing CAESAR II to skip the eigensolution
(reusing the results of the earlier analysis), and only perform the computations for displacements, reactions, forces, and
stresses. Activating this option is only valid after an initial eigensolution has been performed and is still available.
Additionally, the mass and stiffness parameters of the model must be unchanged or the previous eigensolution is invalid.
5-58 Controlling the Dynamic Solution
Spatial or Modal Combination First
(Active for: Spectrum)
This directive tells CAESAR II whether to combine the Spatial components or the Modal components of the load case first.
When performing a spectrum analysis, each of the modal responses must be summed. In addition, if multiple shocks have
been applied to the structure in more than one direction, the results from different directions must be combinedfor
example, spatially combining the X-direction, Y-direction, and Z-direction results. The question arises as to whether the
spatial summations should precede or follow the modal summations. A difference in the final results (of Spatial first vs.
Modal first) arises whenever different methods are used for the spatial and modal combinations.
The combination of Spatial components first implies that the shock loads are dependent, while the combination of Modal
components first implies that the shock loads are independent.
Dependent and Independent refer to the time relationship between the X, Y, and Z components of the earthquake. With a
dependent shock case, the X, Y, and Z components of the earthquake have a direct relationshipa change in the shock
along one direction produces a corresponding change in the other directions. For example, this would be the case when the
earthquake acts along a specific direction having components in more than one axissuch as when a fault runs at a 30
angle between the X- and Z-axes. In this case, the Z-direction load would be a scaled (by a factor of tan 30), but otherwise
identical version of the X-direction load. In this case, spatial combinations should be made first.
An Independent shock is one where the X, Y, and Z time histories produce related frequency spectra but have completely
unrelated time histories. It is the Independent type of earthquake that is far more common, and thus in most cases the modal
components should be combined first.
For example, IEEE 344-1975 (IEEE Recommended Practices for Seismic Qualification of Class 1E Equipment for Nuclear
Power Generating Stations) states:
Earthquakes produce random ground motions which are characterized by simultaneous but statistically INDEPENDENT
horizontal and vertical components.
This is usually less of an issue for force spectrum combinations, since normally there are no separate spatial components to
combinei.e., there are not X-, Y-, and Z-shocks acting simultaneously. However, in the event that there is more than one
potential force load (such as when there is a bank of relief valves that can fire individually or in combination), the spatial
combination method may be used to indicate the independence of the loadings. For example, if two relief valves may or
may not fire simultaneously (i.e., they are independent), the two shocks should be defined as being in different directions
(for example, X- and Y-), and the combination method selected should be Modal before Spatial. If under certain
circumstances, the two valves will definitely open simultaneously (i.e., the loadings are dependent), the combination
method should be Spatial before Modal. (Otherwise, the direction defined for a force spectrum loading has no particular
meaning.)
Nuclear Regulatory Guide 1.92 (published in February, 1976) describes the requirements for combining spatial components
when performing seismic response spectra analysis for nuclear power plants.
Note: Since all Time History combinations are done algebraically (in-phase) this parameter has no effect on Time History
results.
Spatial Combination Method (SRSS/ABS)
(Active for: Spectrum)
This parameter is used to define the method for combining the spatial contributions of the shocks in a single spectrum load
case. This option is only used for spectrum runs with more than a single excitation direction. Since directional forces are
usually combined vectorially, this points to a Square Root of the Sum of the Squares (SRSS) combination method as being
most appropriate. An Absolute method is provided for additional conservatism.
Chapter 5 Controlling the Dynamic Solution 5-59
Note: Since all Time History combinations are done algebraically (in-phase) this parameter has no effect on Time History
results.
Modal Combination Method (GROUP/10%/DSRSS/ABS/SRSS)
(Active for: Spectrum)
During a spectrum analysis, responses are calculated for each of the individual modes; these individual responses are then
combined to get the total system response. Considering that the response spectrum yields the maximum response at any time
during the course of the applied load, and considering that each of the modes of vibration will probably have different
frequencies, it is probable that the peak responses of all modes will not occur simultaneously. Therefore an appropriate
means of summing the modal responses must be considered.
Nuclear Regulatory Guide 1.92 (published in February, 1976) defines the requirements for combining modal responses
when performing seismic response spectra analysis for nuclear power plants. The four options presented there are also
available, along with one other, for modal combinations under non-nuclear seismic and force spectrum analyses.
There are five available modal combination methods:
Grouping Method
Ten Percent Method
Double Sum Method
Absolute
Square Root of the Sum of the Squares
Grouping Method
This method is defined in USNRC Regulatory Guide 1.92. The Grouping Method attempts to eliminate the drawbacks of
the Absolute and SRSS methods (see below) by assuming that modes are completely correlated with any modes with similar
(closely spaced) frequencies, and are completely uncorrelated with those modes with widely different frequencies.
Therefore, the total system response is calculated as
1/ 2
2
1
1
(where 1 )
N
j P j
q m i lq mq l i
k
R Rk R R m
= = =
=
(
= + + + =
(
Where:
R = total system response of the element
N = number of significant modes considered in the modal response combination
R
k
= the peak value of the response of the element due to the kth mode
P = number of groups of closely-spaced modes (where modes are considered to be closely-spaced if
their frequencies are within 10% of that of the base mode in the group), excluding individual separated
modes. No mode can be in more than one group.
i = number of first mode in group q
j = number of last mode in group q
R
lq
= response of mode l in group q
R
mq
= response of mode m in group q
5-60 Controlling the Dynamic Solution
Effectively, this method dictates that the responses of any modes which have frequencies within 10% of each other first be
added together absolutely, with the results of each of these groups then combined with the remaining individual modal
results using the SRSS method.
Note: The 10% figure controlling the definition of a group may be changed by using the Closely Spaced Mode
Criteria/Time History Time Step (ms) parameter. For more information see the corresponding section earlier in this
chapter.
Ten Percent Method
This method is defined in the USNRC Regulatory Guide 1.92. The Ten Percent Method is similar to the Grouping method
in that it assumes that modes are completely correlated with any modes with similar (closely spaced) frequencies, and are
completely uncorrelated with those modes with widely different frequencies. The differences between this one and the
preceding method is that the Grouping Method assumes that modes are only correlated with those that fall within the group
-i.e., are within a 10% band, while this method assumes that modes are correlated with those that fall within 10% of the
subject mode- effectively creating a 20% band - 105 up and approximately 10% down. The total system response is
calculated as
1/ 2
2
1
2 (Where i j)
=
(
= + =
(
N
i j
k
R Rk R R
Where:
R
i
, R
j
= the peak value of the response of the element due to the ith and jth mode, respectively, where
mode i and j are any frequencies within 10% of the each other,
Where:
(fi, fj) / fi = frequencies of modes i and j, respectively
Note: The 10% figure controlling the definition of closely spaced frequencies may be changed by using the Closely Spaced
Mode Criteria/Time History Time Step (ms) parameter. (See description in corresponding section earlier in this chapter).
Double Sum Method (DSRSS)
This method is also defined in USNRC Regulatory Guide 1.92. This combination method is the most technically correct for
earthquake loads, in that an attempt is made to estimate the actual intermodal correlation coefficient based upon empirical
data. The total system response is calculated as
Where:
R
s
= the peak value of the response of the element due to mode s
e
ks
= intermodal correlation coefficient
= [ 1 + {( e
k
' - e
s
') /(
k
' e
k
+
s
' e
s
)}
2
]
-1
e
k
' = e
k
[ 1 -
k
2
]
1/2
e
s
' = e
s
[ 1 -
s
2
]
1/2
k
' =
k
+ 2 / ( t
d
e
k
)
s
' =
s
+ 2 / ( t
d
e
s
)
e
k
= frequency of mode k, rad/sec
Chapter 5 Controlling the Dynamic Solution 5-61
e
s
= frequency of mode s, rad/sec
k
= ratio of damping to critical damping of mode k, dimensionless
s
= ratio of damping to critical damping of mode s, dimensionless
t
d
= duration of earthquake, sec
Note: The load duration (t
d
) and the damping ratio () may be specified by using the Load Duration (Time History or
DSRSS method) (sec.) and Damping (Time History or DSRSS) (ratio of critical) parameters described in the
corresponding sections found earlier in this chapter.
Absolute Method
This method states that the total system response is equal to the sum of the absolute values of the individual modal
responses. (This is effectively the same as using the DSRSS method with all correlation coefficients equal to 1.0, or the
Grouping method, with all modes being closely spaced.) The total system response is calculated as:
1
N
i
i
R R
=
=
This method gives the most conservative result, since it assumes that the all maximum modal responses occur at exactly the
same time during the course of the applied load. This is usually overly-conservative, since modes with different natural
frequencies will probably experience their maximum DLF at different times during the load profile.
Square Root of the Sum of the Squares (SRSS)
This method states that the total system response is equal to the square root of the sum of the squares of the individual
modal responses. (This is effectively the same as using the DSRSS method with all correlation coefficients equal to 0.0, or
the Grouping method, with none of the modes being closely spaced.) The total system response is calculated as:
1/ 2
2
1
N
i
i
R R
=
(
=
(
This method is based upon the statistical assumption that all modal responses are completely independent, with the maxima
following a relatively uniform distribution throughout the duration of the applied load. This is usually non-conservative,
especially if there are any modes with very close frequencies, since those modes will probably experience their maximum
DLF at approximately the same time during the load profile.
Note: Since all Time History combinations are done algebraically (in-phase) this parameter has no effect on Time History
results.
Include Pseudostatic (Anchor Movement) Components (Y/N)
(Active for: Spectrum/ISM)
This option is only used when Independent Support Motion (anchor movement) components are part of a shock load case.
The excitation of a group of supports produces both a dynamic response and a static response. The static response is due to
the movement of one group of supports or anchors relative to another group of supports/anchors. These static components of
the dynamic shock loads are called pseudostatic components. USNRC recommendations, as of August 1985, suggest that
the following procedure be followed for pseudostatic components:
1 For each support group, the maximum absolute response should be calculated for each input direction.
2 Same direction responses should then be combined using the absolute sum method.
3 Combination of the directional responses should be done using the SRSS method.
5-62 Controlling the Dynamic Solution
4 The total response should be formed by combining the dynamic and pseudostatic responses, using the SRSS method.
Therefore pseudostatic components should be included whenever Independent Support spectral loadings are used.
Include Missing Mass Components (Y/N)
(Active for: Spectrum and Time History)
During spectrum (either seismic or force spectrum) or time history analyses, the response of a system under a dynamic load
is determined by superposition of modal results. One of the advantages of this type of modal analysis is that usually only a
limited number of modes are excited and need to be included in the analysis. The drawback to this method is that although
displacements may be obtained with good accuracy using only a few of the lowest frequency modes, the force, reaction, and
stress results may require extraction of far more modes (possibly far into the rigid range) before acceptable accuracy is
attained.
CAESAR II provides a feature, called the Missing Mass Correction, which helps solve these problems. This feature offers
the ability to include a correction which represents the contribution of the higher order modes not explicitly extracted for the
modal/dynamic response, thus providing greater accuracy without additional calculation time. When this option is activated
(by entering Yes for this parameter), the program automatically calculates the net (in-phase) contribution of all non-
extracted modes and combines it with the modal contributionsavoiding the long calculation time associated with the
extraction of the high order modes and the possible excessive conservatives of the summation methods. This feature is
described in Chapter 6 of this manual.
Pseudostatic (Anchor Movement) Comb. Method (SRSS/ABS)
(Active for: Spectrum)
This directive specifies the method by which the pseudostatic responses (see description in the earlier section Include
Pseudostatic (Anchor Movement) Components (see "Include Pseudostatic (Anchor Movement) Components (Y/N)" on page
5-61)) are to be combined with the dynamic (inertial) responses; therefore it is applicable only when there is at least one
Independent Support Motion excitation component in a shock load case. Pseudostatic combinations are done after all
directional, spatial, and modal combinations. Absolute combination gives conservative results, but, as noted in the section
Include Pseudostatic (Anchor Movement) Components, the USNRC recommends using the SRSS method for pseudostatic
combinations.
Missing Mass Combination Method (SRSS/ABS)
(Active for: Spectrum)
This directive defines the method used to combine the missing mass/force correction components (see description in an
earlier section, Include Missing Mass Components (see "Include Missing Mass Components (Y/N)" on page 5-62)) with the
modal (dynamic) results. Research suggests that the modal and rigid portions of the response are statistically independent,
so the SRSS combination method (CAESAR IIs default) is usually most accurate. The Absolute combination method
provides a more conservative result, based upon the assumption that the modal maxima occur simultaneously with the
maximum ground acceleration. Missing mass components are combined following the modal combination.
Note: Even though missing mass components may be included during Time History analyses, all Time History
combinations are done algebraically (in-phase), so this parameter has no effect on Time History results.
Directional Combination Method (SRSS/ABS)
(Active for: Spectrum)
This directive specifies the method used for combining shock components acting in the same direction. This directive is
used most typically with Independent Support Motion load cases, where it defines the way in which responses from
different support groups caused by excitation in the same direction are combined. Additionally, if there are multiple uniform
Chapter 5 Controlling the Dynamic Solution 5-63
shock spectra acting in the same direction (although this is unusual), this directive would govern their combination. In
general, directional combinations should be made using the absolute method. (As noted in the earlier section, Include
Pseudostatic (Anchor Movement) Components (see "Include Pseudostatic (Anchor Movement) Components (Y/N)" on page
5-61), this is the USNRC recommendation for directional combination of pseudostatic responses.) However, in the case of
force spectrum loads, if several loads (for example, several relief valve loads) are all defined with the same shock
direction, using an SRSS combination method would be a way of modeling these as independent loads, while using the
Absolute method would model them as dependent loads.
Note: Since all Time History combinations are done algebraically (in-phase) this parameter has no effect on Time History
results.
Sturm Sequence Check on Computed Eigenvalues (Y/N)
(Active for: Spectrum, Modal, and Time History)
In almost all cases, the eigensolver will detect modal frequencies from the lowest frequency to the highest. Sometimes,
when there is some strong directional dependency in the system, the modes may converge in the wrong order. This could
cause a problem if the eigensolver reaches the cutoff number of modes (i.e., 20), but has not yet found the 20 modes with
the lowest frequency (it may have found modes 1 through 18, 20, and 21, and would have found number 19 next).
CAESAR II checks for this anomaly using the Sturm Sequence calculation. This procedure determines the number of modes
that should have been found between the highest and lowest frequencies found, and compares that against the actual number
of modes extracted. If those numbers are different, the user is given a warning. For example, if 22 natural frequencies are
extracted for a particular system, and if the highest natural frequency is 33.5 Hz, the Sturm Sequence check makes sure that
there are exactly 22 natural frequencies in the model between zero and 33.5+p Hz, where p is a numerical tolerance found
from:
10
Log [(Highest Eigenvalue)-(Number of Significant Figures+1.5)]
10
p=
2l
The Sturm Sequence check would fail in the case where there are two identical frequencies at the last frequency extracted.
The significance of this failure can only be estimated by the user. For example, consider a system with the following natural
frequencies:
0.6637 1.2355 1.5988 4.5667 4.5667
If the user asks for only the first four natural frequencies, a Sturm Sequence failure would occur because there are five
frequencies, rather than four, which exist in the range between 0.0 and 4.5667 + p (where p calculates to 0.0041). To correct
this problem, the user can do either of the following:
Increase the frequency cutoff by the number of frequencies not found. (This number is reported by the Sturm Sequence
Check.)
Increase the cutoff frequency by some small amount, if the frequency cutoff terminated the eigensolution. This will
usually allow the lost modes to fall into the solution frequency range.
Fix the subspace size at 10 and rerun the job. Increasing the number of approximation vectors improves the possibility that
at least one of them will contain some component of the missing modes, allowing the vector to properly converge.
The default here is Yes, and should be left alone unless the user has some specific reason for deactivating the check.
5-64 Controlling the Dynamic Solution
Advanced Parameters
Estimated Number of Significant Figures in Eigenvalues
(Active for: Spectrum, Modal, and Time History)
This is the approximate number of significant figures in the computed eigenvalues (e
2
, where e is the angular frequency in
rad/sec). For example, using the default value of 6, if a computed eigenvalue was 44032.32383, then the first digit to the
right of the decimal is probably the last accurately computed figure.
The eigenvectors, or mode shapes, are computed to half as many significant figures as are the eigenvalues. If the
eigenvalues have 6 significant figures of accuracy, then the eigenvectors have 3.
This number should typically never be decreased. Increases to 8 or 10 are not unusual but result in slower solutions with
typically little change in response results.
Jacobi Sweep Tolerance
(Active for: Spectrum, Modal, and Time History)
Eigen analyses are done using an NxN subspace for calculating the natural frequencies and mode shapes for a reduced
problem. The first step is to perform a Jacobi denationalization of the subspace. Iterations are performed until the off-
Chapter 5 Controlling the Dynamic Solution 5-65
diagonal terms of the matrix are approximately zero. The off-diagonal terms are considered to be close enough to zero when
their ratio to the on-diagonal term in the row is smaller the Jacobi Sweep Tolerance.
The default is 1.0E-12. Users wishing to change this value should be aware of the computers precision (the IEEE-488
double precision word on the IBM PC has approximately 14 significant figures) and the approximate size of the on-diagonal
coefficients in the stiffness matrix for the problem to be solved (which may be estimated from simple beam expressions).
Decomposition Singularity Tolerance
(Active for: Spectrum, Modal, and Time History)
During the eigensolvers decomposition of what may be a shifted stiffness matrix, a singularity check is performed to make
sure that the shift is not too close to an eigenvalue that is to be calculated. If a singular condition is detected, a new shift, not
quite as aggressive as the last one, is computed and a new decomposition is attempted. If the new composition fails, a fatal
error is reported from the eigensolver. In certain cases, increasing the singularity tolerance is warranted and eliminates this
fatal error. Values should not be entered greater than 1.0 E13. Singularity problems may also exist when very light, small
diameter piping is attached to very heavy, large diameter, or when very, very short lengths of pipe are adjacent to very, very
long lengths of pipe.
Subspace Size (0-Not Used)
(Active for: Spectrum, Modal, and Time History)
During an eigensolution, the NDOFxNDOF problem constructed by the user is reduced to an NxN problem during each
subspace iteration, where N is the subspace size. If a zero is entered in this field, CAESAR II selects what is expected to be an
optimal subspace size (so this value usually need not be changed); if a non-zero value is entered here, it will override
CAESAR IIs calculation and will be used as the subspace size.
CAESAR IIs default is to use the square root of the bandwidth (with a minimum of 4) as the subspace size, resulting in sizes
of 4 to 8 for typical piping configurations. Increasing the subspace size slows the eigensolution, but increases the numerical
stability. Values in the range between 12 and 15 should probably be used when unusual geometries or dynamic properties
are encountered, or when a job is large (has 100 elements or more, and/or requires that 25 or more frequencies be extracted).
No. to Converge Before Shift Allowed (0 - Not Used)
(Active for: Spectrum, Modal, and Time History)
A zero in this field lets CAESAR II select what it thinks will be the most optimal shifting strategy for the eigen problem to be
solved. One way to speed the eigensolution is to improve the convergence characteristics. The convergence rate for the
lowest eigenpair in the subspace is inversely proportional to e
1
/ e
2
, where e
1
is the lowest eigenvalue in the current
subspace and e
2
is the next lowest eigenvalue in the current subspace. A slow convergence rate is represented by an
eigenvalue ratio of approximately one, and a fast convergence rate is represented by an eigenvalue ratio of zero. The shift is
employed to get the convergence rate as close to zero as possible. The cost of each shift is one decomposition of the system
set of equations. The typical shift value is equal to the last computed eigenvalue plus 90 percent of the difference between
this value and the lowest estimated eigenvalue still nonconverged in the subspace. As e
1
is shifted closer to zero, the ratio
e
1
/e
2
will become increasingly smaller thus increasing the convergence rate. In certain instances where eigenvalues are
very closely spaced, shifting can result in eigenvalues being lost (the Sturm Sequence Check will detect this condition). A
large value entered for this parameter will effectively disable shifting, so no eigenvalues will be missed; however, the
solution will take longer to run. When the system to be analyzed is very large, shifting the set of equations can be very time
consumingin these cases, the user is advised to set this parameter to somewhere between 4 and 8.
No. of Iterations Per Shift (0 - Pgm computed)
(Active for: Spectrum, Modal, and Time History)
5-66 Controlling the Dynamic Solution
A zero in this field lets CAESAR II compute what it thinks is an optimal number of subspace iterations per shift. This
parameter, along with the next one (% of iterations per shift before orthogonalization) can work together to control solution
shifting. These two parameters are used to limit the number of Gram-Schmidt orthogonalizations that are performed. Trying
to limit this number is very dangerous for small subspace problems, but less dangerous when the subspace size is large
(around 10-20 percent of the total number of eigenpairs required).
The Gram-Schmidt orthogonalization is by default performed once during each subspace iteration. This orthogonalization
makes sure that the eigenvector subspace does not converge to an already found eigenpair. When a large number of
eigenpairs are to be computed this repeated computation can appreciably slow down the extraction of the highest eigenpairs.
Proper setting of these parameters can cause the eigensolution to perform the orthogonalization every second, third, fourth,
etc. iteration, thus speeding the solution. Unfortunately, once orthogonalized, the subspace may still converge to earlier
eigenpairs during subsequent non-orthogonalized subspace iteration passes. Users setting these parameters are urged to
use caution. The Force Orthogonalization After Convergence (see "Force Orthogonalization After Convergence (Y/N)" on
page 5-66) parameter (see corresponding section later in this chapter) should probably also be set if the frequency of
orthogonalization is slowed.
Percent of Iterations Per Shift Before Orthogonalization
(Active for: Spectrum, Modal, and Time History)
CAESAR II computes a number of iterations per shift that are to be performed, which the user can alter if desired. A
maximum of N eigenpairs can conceivably converge per subspace pass, where N is the subspace size (although this is
highly unlikely). By default a Gram-Schmidt orthogonalization is performed for each subspace pass. This directive allows
the user to alter this default. For example, if there are 12 iterations per shift, and the percentage of iterations per shift is 50
percent (an entry of 0.50), the Gram-Schmidt orthogonalization would be performed every 6 iterations. Users employing
this option should also set the Force Orthogonalization After Convergence (see "Force Orthogonalization After
Convergence (Y/N)" on page 5-66) directive to Yes. The Percent of Iterations per Shift Before Orthogonalization
parameter is most often used in conjunction with the No. of Iterations per Shift (see "No. of Iterations Per Shift (0 - Pgm
computed)" on page 5-65) parameter because then the user knows exactly how many iterations will go by without an
orthogonalization.
Force Orthogonalization After Convergence (Y/N)
(Active for: Spectrum, Modal, and Time History)
This parameter is only needed for eigensolutions for which the Percent of Iterations per Shift Before Orthogonalization
(on page 5-66) (the previous section) has been set to a non-zero value. When set to Yes in this case, whenever a subspace
pass that sees at least one eigenpair convergence completes, a Gram-Schmidt orthogonalization is performed whether the
specified percentage of iterations has been completed or not.
Use Out-Of-Core Eigensolver (Y/N)
(Active for: Spectrum, Modal, and Time History)
This parameter is used primarily as a benchmarking and debugging aid. When entered as Yes, the out-of-core eigensolver
is automatically invoked regardless of the problem size. Using this solver can take considerably more time than the in-core
solver, but should in all cases produce exactly the same results. Note that if the problem is too big to fit into the in-core
solver (the capacity of which is based upon the amount of available extended memory), the out-of-core solver will be
invoked automaticallythis parameter does not need to be changed to have this automatic switch occur when necessary.
Frequency Array Spaces
(Active for: Spectrum, Modal, and Time History)
This is the maximum number of eigenpairs that can be extracted for the problem. The default value of 100 is arbitrary. If the
user needs to extract more than 100 eigenpairs, then some number greater than the number to be extracted must be entered.
Chapter 5 Controlling the Dynamic Solution 5-67
Pulsation Loads
Unexpectedly, and sometimes after support changes or process modifications, an operating line will begin experiencing
large amplitude, low frequency vibration. The first step in the solution is the construction of the dynamic model. Particular
attention should be paid when modeling the piping system in the area of the field vibration. This might include accurately
representing valve operators, in-line flange pairs, orifice plates and measuring equipment. It is also a good idea to add extra
nodes in the area where vibration is experienced. The extra nodes would be put at bend near nodes and at span midpoints.
The next step is the eigenvalue/eigenvector extraction. If the system is large, then degrees of freedom far removed from the
area of local vibration should be eliminated and (6-10) natural frequencies should be extracted. Natural frequencies and
mode shapes define the systems tendency to vibrate. The mode shapes extracted should show how the system in the area
of the local vibration problem is tending to displace. In most cases acoustic resonances are coupled with mechanical
resonances to produce the large amplitude vibrations experienced in the field.
Very typically one of the first mode shapes will show exactly the shape displayed by the pipe vibrating in the field. If the
mode shapes extracted do not show movement in the area of the local vibration, then not enough degrees of freedom were
removed from other areas. If the lowest mode shape in the area of the local vibration problem is above (15) Hz. then there is
a good possibility that either the vibration is mechanically induced or the fluid pulsation peak pressures are very high. Either
of these cases may represent critical situations which should be evaluated by an expert.
When the mode shape is identified which corresponds to the observed field vibration, the pulsation load model can be
developed. Pulsation loads will exist at closed ends, at bends, and at changes in diameter. Harmonically varying forces are
put at these points in an attempt to get the mathematical model to vibrate like the real piping system. The driving frequency
for the applied harmonic load should be equal to the frequency that pressure pulses are introduced into the line. The
magnitude of the harmonic load can be estimated within a range of tolerances. The actual design value is selected from this
range such that resulting displacements of the model are close to those observed in the field.
Output from the harmonic analysis can be processed in the static output processor and maximum restraint loads due to the
dynamic forces calculated. It is critical when redesigning supports for dynamic loads that static thermal criteria are not
violated by any new support configuration designed.
Important: Static thermal criteria and dynamic displacement criteria must be satisfied simultaneously.
The ultimate objective of the harmonic analysis will be to find the elbow pair whose unbalanced load results in the observed
field vibration.
Unbalanced loads exist between adjacent elbows because the pressure peak in the traveling wave hits each elbow at a
slightly different time.
If the pressure at elbow a is denoted by Pa(t) and the pressure at elbow b is denoted by Pb(t), then the unbalanced force
which acts along the pipe connecting the two elbows is:
F = A * Pa(t) - A * Pb(t) EQ. (1)
Where A is the inside area of the pipe. The expression for Pa(t) can be found assuming the pressure peak hits the elbow a
at time t = 0:
Pa(t) = Pavg + 0.5 (dP) cos et EQ. (2)
Where:
(Pavg) - average pressure in the line,
(dP) - alternating component of the pressure, (Pmax-Pmin)
(e) - driving frequency.
5-68 Controlling the Dynamic Solution
If the straight pipe between the elbows a and b is (L) inches long, then the pressure peak that has just passed elbow a
will get to elbow b (ts) seconds later, where
(t
s
) = (L) / c,
(c) being the speed of sound in the fluid. (Remember, pressure pulses travel at the speed of sound, not the speed of the fluid
! ! !) The expression for the pressure at b can now be written:
Pb(t) = Pavg + 0.5(dP) cos (et + Q) EQ.(3)
Q is the phase shift between the pressure peaks at a and b,
Q = e * (t
s
). (Where Q is in radians, and e is in radians/second)
Combining equations 1, 2, and 3 the unbalanced pressure force can be written:
F(t) = 0.5(dP)A * [ cos et - cos (et-Q) ]
This function has a maximum:
Fmax = 0.5(dP)A sin Q/cos (Q/2)
and a period of 1/w, and will be approximated with:
f(t) = 0.5(dP)A (sin Q/cos (Q/2)) cos et
The formulation of the harmonic loads can be summarized as follows:
1 Decide which elbow-elbow pair is most likely to have an unbalanced force which could cause the displacements
observed in the field.
2 Find upper and lower estimates for the following variables:
dP Alternating pressure in the line (Pmax - Pmin)
e Driving frequency.
c Speed of sound in the fluid.
L Length between the two elbows.
A Area of the pipe.
3 Find the time it takes the pressure wave to get from one elbow to the other.
t
s
= L / (c-)
(c-) is the lower estimate for the speed of sound in the fluid.
4 Find the largest estimated magnitude of the unbalanced pressure force:
Fmax = (0.5) (dP+)A * sin [(e+) (t
s)
] / cos [(et) (t
s
)/2]
(dP+) is the upper estimate for the alternating pressure.
(e+) is the upper estimate for the driving frequency.
5 Run a single harmonic analysis with a force of F = Fmax [cos (et)] acting along the axis of the pipe between the two
elbows. If the pattern of the displacement approximately that seen in the field, and if the magnitude of the calculated
displacement is greater than or equal to the magnitude of the displacement in the field, then the harmonic load to be
used for the design of the new restraints has been found.
Chapter 5 Controlling the Dynamic Solution 5-69
Relief Valve Thrust Load Analysis
There can be two types of destructive dynamic forces associated with relief devices:
Thrust at the valve/atmosphere interface
Acoustic shock due to the sudden change in fluid momentum and the associated traveling pressure wave(s).
The analyst must evaluate the effective contribution of both types of loads. Dynamic forces associated with relieving
devices can cause considerable mechanical damage to equipment and supports. The discussion below concerns only the
thrust at the valve/atmosphere interface. The acoustic traveling pressure wave can be dealt with similar to the water hammer
problem, addressed elsewhere.
The first step in performing a relief load analysis is to compute the magnitudes of the relieving thrust forces. For open-type
vent systems CAESAR II has a RELIEF LOAD SYNTHESIZER that will make these computations automatically for the
user. There are two procedures incorporated into the synthesizer, one is for gases greater than 15 psig, and the other is for
liquids. Both are discussed as follows.
Relief Load Synthesis for Gases Greater Than 15 psig
CAESAR II assumes that a successful vent stack/relief system design maintains the following gas properties:
The input for the gas relief load synthesis is shown as follows:
5-70 Controlling the Dynamic Solution
Line Temperature
Enter the stagnation condition temperature of the gas to be relieved (Usually just the gas temperature upstream of the relief
valve).
Line Pressure
Enter the stagnation pressure of the gas to be relieved (Usually just the gas pressure upstream of the relief valve). Note that
stagnation properties can vary considerably from line properties if the gas flow velocity in the line is high.
ID of Relief Valve Orifice
Enter the flow passage inside diameter for the smallest diameter in the relief valve throat. (This information is usually
provided by the relief valve manufacturer).
ID of Relief Valve Piping
Enter the inside diameter of the piping attached directly to the exhaust of the relief valve.
ID of Vent Stack Piping
If CAESAR II is to size the vent stack then leave this ID blank. If the vent stack piping is the same size as the relief valve
piping, i.e. it is one-in-the-same, then this field may be left blank. Otherwise enter the inside diameter of the vent stack
piping.
Chapter 5 Controlling the Dynamic Solution 5-71
Length of the Vent Stack
Enter the length of the vent stack. This is a required entry. Add double the lengths of fittings and elbows (or compute the
appropriate equivalent lengths for non-pipe fittings and add the lengths).
Some typical values for these constants are given below:
Ratio of Gas-Specific Heats (k) Gas Constant (R) (ft. lbf./lbm./deg. R
Superheated Steam 1.300 Nitrogen 55.16
Saturated Steam 1.100 Carbon Dioxide 35.11
Nitrogen 1.399 Acetylene 59.35
Carbon Dioxide 1.288 Ammonia 90.73
Acetylene 1.232 n-Butane 26.59
Ammonia 1.304 Ethane 51.39
n-Butane 1.093 Ethylene 55.09
Ethane 1.187 Methane 96.33
Ethylene 1.240 Propane 35.05
Methane 1.226
Propane 1.127
Does the Vent Pipe Have an Umbrella Fitting (Y/N)
Enter a Y or a N. See the following figures to determine if the connection of the vent stack to the vent piping is via an
umbrella fitting.
5-72 Controlling the Dynamic Solution
Should CAESAR II Size the Vent Stack (Y/N)
Enter a Y if CAESAR II should size the vent stack. The sizing algorithm searches through a table of available inside pipe
diameters starting at the smallest diameter until a vent stack ID is found that satisfies the thermodynamic criteria shown in
the figure above. The computed ID is automatically inserted into the input.
Example input and output from the relief load synthesizer is shown and discussed as follows:
Relief Load Synthesis Input (Gas)
Relief Load Synthesis Output (Gas)
Chapter 5 Controlling the Dynamic Solution 5-73
Computed Mass Flowrate (Vent Gas)
This is CAESAR IIs computed gas mass flow rate based on choked conditions at the relief orifice. If greater mass flow rates
are expected, then the error in either the approach used by CAESAR II or in the expected mass flow rate should be
investigated.
Thrust at Valve Pipe/Vent Pipe Interface
If there is an umbrella fitting between the vent stack and the relief valve piping then this is the thrust load that acts back on
the relief valve piping. (See the following figure.) If the vent stack is hard piped to the relief valve piping then this
intermediate thrust will be balanced by tensile loads in the pipe and can be ignored.
Thrust load acts directly on valve opening. Only the valve pipe/vent stack interface
thrust acts in this configuration.
Thrust at the Vent Pipe Exit
When there is an elbow in the vent stack piping, this is the thrust load that acts on the elbow just before the pipe opening
into the atmosphere. (See the following figure for clarification.)
Transient Pressure Rise on Valve Opening
This is the estimated magnitude of the negative pressure wave that will be superimposed on the line pressure when the relief
valve fist opens. This negative pressure wave will move back through the relief system piping similar to the pressure wave
in the downstream piping of a water hammer type system. The magnitude of this wave is estimated as (Po-Pa)*Ap, where
Po is the stagnation pressure at the source, Pa is atmospheric pressure, and Ap is the area of the header piping.
Transient Pressure Rise on Valve Closing
The estimated magnitude of the positive pressure wave that will be superimposed on the line pressure when the relief device
slams shut. This positive pressure wave will move back through the relief system piping similar to the pressure wave in the
5-74 Controlling the Dynamic Solution
supply side piping of a waterhammer type system. The magnitude of this wave is estimated from: r*c*dv where r is the fluid
density, c is the speed of sound in the fluid and dv is the change in the velocity of the fluid.
Thermodynamic Entropy Limit /Subsonic Vent Exit Limit
These values should always be greater than 1. If either of these computed limits fall below 1.0 then the thermodynamic
assumptions made regarding the gas properties are incorrect and the computed thrust values should be disregarded.
Valve Orifice Gas Conditions /Vent Pipe Exit Gas Conditions/Subsonic Velocity Gas Conditions
These are the thermodynamic properties of the gas at three critical points in the relief system. These three points are shown
in the figure on the opposite page. The entire formulation for the thrust gas properties is based on an ideal gas equation of
state. If the pressures and temperatures displayed above for the gas being vented are outside of the range where the ideal gas
laws apply then some alternate source should be sought for the computation of the systems thrust loads.
In addition, all three of these points should be sufficiently clear of the gas saturation line. When the exit gas conditions
become saturated, the magnitude of the thrust load can be reduced significantly. In this case the manufacturer should be
consulted. In several instances at COADE, saturated exhaust thrust loads were 50 to 75% less than the CAESAR II computed
values.
Relief Load Synthesis for Liquids
CAESAR II assumes that the liquid vent system has one of the two following configurations:
The input for the liquid relief load synthesis is shown as follows:
Chapter 5 Controlling the Dynamic Solution 5-75
Relief Valve or Rupture Disk
Enter RV if the relieving device is a relief valve and RD if the relieving device is a rupture disk. If the user has his own
relief exit coefficient it can be entered here in place of the letters RV or RD. An entry of zero represents No appreciable
head loss due to the relief opening configuration. The exit coefficient for a relief valve is 0.25 and for a rupture disk is 0.5.
Supply Overpressure
Enter the stagnation, or zero velocity pressure in the fluid upstream of the relief valve.
ID Relief Orifice or Rupture Disk Opening
Enter the manufacturers inside diameter of the contracted opening in the particular relieving device. (For special purpose
calculations this ID may be equal to the ID of the Relief exit piping.)
ID Relief Exit Piping
Enter the inside diameter of the piping connected to the downstream side of the relief valve.
ID Manifold Piping
If the relief exit piping runs into a manifold then enter the inside diameter of the manifold. Leave this field blank or zero if
there isn't a manifold.
ID Supply Header
Enter the inside diameter of the supply header.
Fluid Density
Enter the specific gravity of the fluid being relieved.
Length of Relief Exit Piping
Enter the equivalent length of the relief exit piping. Add twice the piping length for fittings and elbows, or the calculated
fitting equivalent length.
Length of Manifold Piping
Enter the equivalent length of the manifold piping, if any. If there isn't a manifold system then leave this field blank or zero.
Add twice the piping length for fitting and elbows. If the manifold is not filled by the relieving fluid then leave the manifold
length zero.
Fluid Bulk Modulus
Enter the bulk modulus of the fluid. If omitted a valve of 250,000 psi will be used as the default. Some typical values for use
are given as follows. These are the values for an isothermal compression as taken from Marks Standard Handbook for
Engineers, p. 3-35, 8th edition.
Supply Header Pipe Wall Thickness
Enter the wall thickness of the supply header.
Note: When running the relief load synthesis for liquids, the error message: NUMERICAL ERROR OR NO FLOW
CONDITION DETECTED, means a physically impossible configuration was described.
5-76 Controlling the Dynamic Solution
Flashing of volatile relief liquids is not considered. If the relieving liquid flashes in the exhaust piping as its pressure drops
to atmospheric then some other means should be used to compute the resulting gas properties and thrust loads.
Output From the Liquid Relief Load Synthesizer
Computed Mass Flow Rate
The computed exhaust mass flow rate in U.S. Gallons per minute. CAESAR II makes the necessary pressure drop calculations
between the stagnation pressure upstream of the relief device and atmospheric conditions at the exit of the manifold.
Thrust at the End of the Exit Piping
The computed thrust load at the last cross section in the exit piping. If there is no manifold then this is the external thrust
load that acts on the piping system. If there is a manifold then this thrust is opposed by tension in the pipe wall at the
junction of the exit piping and manifold. See the figures that follow for clarification.
Thrust at the End of the Manifold Piping
The computed thrust load at the last cross section in the manifold piping. If there is no manifold system then this thrust will
be equal to the thrust at the end of the exit piping. See the figures that follow for clarification.
Transient Pressure Rise on Valve Opening
This is the estimated magnitude of the negative pressure wave that will be superimposed on the line pressure when the relief
valve fist opens. This negative pressure wave will move back through the relief system piping similar to the pressure wave
in the downstream piping of a water hammer type system. The magnitude of this wave is estimated as (Po-Pa)*Ap, where
Po is the stagnation pressure at the source, Pa is atmospheric pressure, and Ap is the area of the header piping.
Transient Pressure Rise on Valve Closing
The estimated magnitude of the positive pressure wave that will be superimposed on the line pressure when the relief device
slams shut. This positive pressure wave will move back through the relief system piping similar to the pressure wave in the
supply side piping of a waterhammer type system. The magnitude of this wave is estimated from: r*c*dv where r is the fluid
density, c is the speed of sound in the fluid and dv is the change in the velocity of the fluid.
Orifice Flow Conditions/Exit Pipe End Flow Conditions/Manifold Pipe End Flow Conditions
These are the computed fluid properties at the three critical cross-sections in the relief piping. If pressures or velocities here
do not seem reasonable then some characteristic of the relief model is probably in error.
Chapter 5 Controlling the Dynamic Solution 5-77
Note: If the L dimensions are significant in any of the previous figures (several feet) then unbalanced thrust loads will
act between the elbow-elbow pairs that are very similar to a water hammer load. Water hammer pulses travel at the speed of
sound in the fluid, while the fluid/atmosphere interface pulses travel at the velocity of the flowing fluid. For this reason,
these unbalanced loads can cause significant piping displacements in much shorter pipe runs. The magnitude of these loads
is equivalent to the computed thrust and the duration may be found from the computed fluid velocity and distance between
each elbow-elbow pair.
Chapter 6 Technical Discussions
This chapter includes a more detailed discussion of implementations, methods, and assumptions.
In This Chapter
Rigid Element Application ...................................................................... 6-2
In-line Flange Evaluation ........................................................................ 6-3
Cold Spring.............................................................................................. 6-5
Expansion Joints ...................................................................................... 6-7
Hanger Sizing Algorithm......................................................................... 6-9
Class 1 Branch Flexibilities ..................................................................... 6-12
Modeling Friction Effects........................................................................ 6-15
Nonlinear Code Compliance.................................................................... 6-16
Sustained Stresses and Nonlinear Restraints ........................................... 6-17
Static Seismic Loads................................................................................ 6-20
Wind Loads.............................................................................................. 6-22
Hydrodynamic (Wave and Current) Loading .......................................... 6-25
Evaluating Vessel Stresses....................................................................... 6-36
Inclusion of Missing Mass Correction..................................................... 6-40
Fatigue Analysis Using CAESAR II........................................................ 6-44
Pipe Stress Analysis of FRP Piping......................................................... 6-60
Code Compliance Considerations............................................................ 6-81
Local Coordinates.................................................................................... 6-112
C H A P T E R 6
6-2 Technical Discussions
Rigid Element Application
CAESAR II forms rigid elements by multiplying the wall thickness of the element by 10. The inside diameter, and the weight
of the element, remain unchanged. The rigid element in CAESAR II is rigid relative to the pipe around it. If a 6-in. line ties
into a 72-in. heat exchanger, then the rigid elements modeling the heat exchanger should have a diameter closer to 72 than
6. The user that is sensitive to the rigidness of the rigid element can increase or decrease the diameter or wall thickness of
the rigid to simulate any order of magnitude stiffness.
Rigid Material Weight
The weight of the rigid element is entered by the user. If no value is input then the weight of the rigid is taken to be zero.
The entered weight is the weight of the rigid excluding insulation or fluid. If the weight of the rigid element is entered as
zero or blank, then no additional weight due either to insulation or fluid will be added.
Rigid Fluid Weight
CAESAR II automatically adds fluid loads for rigid elements if a non-zero fluid density is entered on the pipe spreadsheet.
The fluid weight in a rigid element is assumed to be equal to the fluid weight in an equivalent straight pipe of similar length
and inside diameter.
Rigid Insulation Weight
CAESAR II also automatically adds insulation loads if the line containing the rigid element is insulated. The insulation
weight for the rigid is assumed to be equal to 1.75 times the insulation for an equivalent length of straight pipe of equal
outside diameter.
The cumulative rigid element weight calculation is as follows:
Weight = 0.0 W
u
= 0.0
Weight = W
u
+ W
f
+ 1.75W
i
W
u
> 0.0
Where:
W
u
= User entered rigid weight
W
f
= Calculated fluid weight for equivalent straight pipe
W
i
= Calculated insulation weight for equivalent straight pipe
The user-entered weight for the rigid element is not reflected in the Thermal Expansion/Pipe Weight Report optionally
printed during error checking.
Stresses are not calculated on Rigid elements since they are often used to simulate components that have variable cross-
sections along the length of the element, i.e. a valve, and is normally not of concern for this type of analysis anyway. Forces
and Moments are not normally printed on nodes between two rigid elements, but can be by selecting the appropriate check
box found in Environment-Special Execution Parameters from the Piping Input Spreadsheet.
Zero-weight rigids ("dummy" rigids) are often used to model components whose weight is not important to the analysis, but
where thermal growth may be a consideration. Dummy rigids are often used to model restraints. Tie rods in an expansion
joint, rod hangers, and trunnions are examples of restraints modeled as dummy rigids. Dummy rigids may also be used to
provide connectivity between the center line of an element and it's outside edge. The most common example of this is the
addition of a dummy rigid that runs from the node at the center line of the vessel to the edge where a nozzle is to be
connected. Sometimes equipment is modeled through a series of rigid elements. This is particularly true when multiple
nozzles are attached and the equipment is restrained such that the interactions between the various nozzles must be taken
into account due to the thermal growth of the attached piping system. The use of dummy rigids is explained in the
CAESAR II Applications Guide in various sections as appropriate to a particular modeling technique.
Chapter 6 Technical Discussions 6-3
In-line Flange Evaluation
CAESAR II offers two methods for evaluating flanges under load:
Kellogg Equivalent Pressure Method
The Kellogg Equivalent Pressure Method converts piping axial forces and bending moments into a Equivalent Pressure
on the flange, which is then added to the Design Pressure, the total of which is then compared to the allowable pressure
rating for the flange at the appropriate temperature. The exact calculations are:
P
eq
= 16M/(t)G
3
+ 4F/ (t)G
2
+ P
D
Where:
P
eq
= equivalent pressure (for checking against flange rating)
M = bending moment on flange
G = diameter of effective gasket reaction
F = axial force on flange (where forces are always taken as an absolute value)
P
D
= design pressure
Note: CAESAR IIs implementation increases the allowable pressure rating by the Occasional Stress factor where one exists
for the load case type/code combination.
ASME NC-3658.3 Calculation for B16.5 Flanged Joints with High Strength Bolting Method
Note that use of this method should be restricted to joints using flanges, bolting, and gaskets as specified in ANSI B16.5
which use bolting materials having an S value at 100F (38C) not less than 20,000 psi (138 MPa). The analysis method for
Service Level A has been implemented in CAESAR II. As stated in NC-3658.3(a)(2):
Mfs @ 3125(Sy/36,000)CA
b
or
Mfd @ 6250(Sy/36,000)CA
b
Where:
M
fs
= bending or torsional moment (whichever is greater) acting on the flange, and due to weight,
thermal expansion, sustained anchor movements, relief valve steady state thrust, and other sustained
mechanical loads (CAESAR II considers any moments developed during a non-Occasional Load Case to
be M
fs
)
M
fd
= bending or torsional moment (whichever is greater) acting on the flange, as defined for
Mfs
and
but also including any dynamic loadings (CAESAR II considers any moments developed during an
Occasional Load Case to be M
fd
, effectively doubling flange capacity for Occasional loadings)
Sy = yield strength of flange material at design temperature (CAESAR II allows evaluation to be done at
up to 10 different temperatures); Sy/36,000 (where Sy, given in psi, shall not be taken as greater than
36,000 psi)
C = bolt circle diameter
A
b
= total cross sectional area of bolts
P
D
= design pressure
6-4 Technical Discussions
CAESAR IIs implementation calculates an Equivalent Stress S in the flange, which is then compared to Sy (or 2*Sy for
Occasional Load Cases), in the following manner:
S = 36,000* Mfs / (CA
b
* 3125) @ Min(Sy, 36000) (non-Occ)
S = 36,000 * Mfd / (CA
b
* 3125) @ 2.0 * Min(Sy, 36000) (Occ)
Note that for systems of units not expressing stresses in PSI, the 36,000 values in the above equations are converted to the
appropriate set of units.
Note: Flange Evaluation has only been implemented for Static Analysis, but not yet for Dynamic (including Harmonic)
Analysis.
Chapter 6 Technical Discussions 6-5
Cold Spring
Cold spring is the process of offsetting (or pre-loading) the piping system with displacement loads (usually accomplished by
cutting short or long the pipe runs between two anchors) for the purpose of reducing the absolute expansion load on the
system. Cold spring is used to do the following:
hasten the thermal shakedown of the system in fewer operating cycles
reduce the magnitude of loads on equipment and restraints, since often, only a single application of a large load is
sufficient to damage these elements
Several things should be considered when using cold spring:
Cold reactions on equipment nozzles due to cold spring should not exceed nozzle allowables.
The expansion stress range should not include the effect of the cold spring.
The cold spring should be much greater than fabrication tolerances.
Note: No credit can be taken for cold spring in the stress calculations, since the expansion stress provisions of the piping
codes require the evaluation of the stress range, which is unaffected by cold spring (except perhaps in the presence of non-
linear boundary conditions, as discussed below). The cold spring merely adjusts the stress mean, but not the range.
Many engineers avoid cold spring due to the difficulty of maintaining accurate records throughout the operating life of the
unit. Future analysts attempting to make field repairs or modifications may not necessarily know about (and therefore
include in the analysis) the cold spring specification.
Due to the difficulty of properly installing a cold sprung system, most piping codes recommend that only 2/3 of the
specified cold spring be used for the equipment load calculations.
The cold spring amount is calculated as:
C
i
= 1/2L
i
o dT
6-6 Technical Discussions
Where:
C
i
= length of cold spring in direction i (where i is X, Y, or Z), (inches)
L
i
= total length of pipe subject to expansion in direction i, (inches)
o = mean thermal expansion coefficient of material between ambient and operating temperature,
(in/in/F)
dT = change in temperature, (F)
Note that the 1/2 in the equation for the cold spring amount is used such that the mean stress is zero. In some cases it is
desirable to have the operating load on the equipment as close to zero as possible. In this latter case the 1/2 should be
omitted. The maximum stress magnitude will not change from a system without cold spring, but will now exist in the cold
case rather than the hot.
To model a cold spring in CAESAR II specify the elements as being made of cut short or cut long materials. Cut short
describes a cold sprung section of pipe fabricated short by the amount of the cold spring, requiring an initial tensile load to
close the final joint. Cut long describes a cold sprung section of pipe fabricated long by the amount of cold spring, requiring
an initial compressive load to close the final joint. The software models cut shorts and cut longs by applying end forces to
the elements sufficient to reduce their length to zero (from the defined length) or increase their length to the defined length
(from zero) respectively. (It should be remembered to make the lengths of these cold spring elements only 2/3 of their actual
lengths to implement the code recommendations.) This is effectively what occurs during application of cold spring. The end
forces applied to the elements are then included in the basic loading case F (for force), whereby they can be included in
various load combinations.
Special material numbers 18 and 19 are used to signal CAESAR II that the element currently in the spreadsheet actually
represents a length of pipe that is to be cut short or long during fabrication.
Material # 18 - Cut Short
Material # 19 - Cut Long
The user should be sure to reset the material property on the element following the cold spring element.
The following load cases are recommended when analyzing a cold spring system:
Load Case 1 (OPE) W+T1+P1+CS includes all of the design cold spring
Load Case 2 (OPE) W+P1+CS includes all of the design cold spring but not the temperature.
Load Case 3 (SUS) W+P1 standard sustained case for Code Stress check
RUN # 1
Load Case4 (EXP) L1-L2 expansion case for code stress check.
Cold spring is allowed to reduce the magnitude of equipment loads because, often, only a single application of a large load
is sufficient to cause damage to rotating machinery.
Cold spring does not change the range of stresses that the piping system is subject to, and so, no allowance is given for
stress reduction. (The maximum value of the stress is lowered, but the range is unchanged.)
Both the sustained loads and the operating loads should be within the manufacturers allowables for the particular piece of
equipment. If the designer isn't careful, the installation of the cold spring in the ambient state can overload a piece of
rotating equipment as the unit starts up.
Chapter 6 Technical Discussions 6-7
Expansion Joints
To define an expansion joint, activate the Expansion Joint check box (see "Expansion Joints" on page 3-20) on the Pipe
Element Spreadsheet.
Expansion joint elements may have a zero or non-zero length. The expansion joint will have a zero length if the Delta fields
in the spreadsheet are left blank or zero. The expansion joint will have a non-zero length if at least one of the elements
spreadsheet Delta fields is non-blank and non-zero. When an expansion joint has a finite length CAESAR II evenly
distributes the expansion joint stiffnesses over the entire length of the element. This will usually result in a more accurate
stiffness model in what is typically a very sensitive area of the piping system.
Four stiffnesses define the expansion joint
Axial Stiffness
Transverse Stiffness
Bending Stiffness
Torsional Stiffness
These stiffnesses are defined as shown in the following figure:
The transverse and the bending stiffnesses are directly related when a finite length joint is defined. In this case the bending
stiffness should be left blank and the transverse stiffness entered. CAESAR II will compute the proper bending stiffness from
the relationship between the bending and transverse stiffnesses. Bending stiffnesses from manufacturers' catalogs should
generally only be entered for zero length expansion joints modeling hinges or gimbals. Before a manufacturers bending
stiffness is used for a finite length bellows it should be multiplied by 4.0 (note that in this case the transverse stiffness would
be left blank).
Torsional stiffnesses are often not given by expansion joint manufacturers. In this case the user is recommended to insert a
large torsional stiffness value and ensure that the resulting load on the bellows is not excessive. When the piping system is
tight, and the diameter large, the magnitude of this large torsional stiffness can significantly affect the magnitude of the
torsion carried by the bellows, i.e. stiffnesses of 100,000 in.lb./deg. and 1E12 in.lb./deg. can produce considerably different
torsional load results. The tendency would be to go with the larger stiffness, i.e. being conservative, except that the torsional
stiffness value is probably closer to the 100,000 in.lb./deg. In the instance where the largeness of the torsional stiffness
6-8 Technical Discussions
value is important, the manufacturer should be pressed for his best-guess at the stiffness, or the following equation should
be used to get an estimate, which the user can then conservatively increase to get reasonable torsional loads on the bellows
and surrounding equipment.
The equation for estimating bellows torsional stiffness is
3
( ) ( )( )
(1 )
Re t E
L
t
+ v
Where
t = 3.14159
Re = Expansion joint effective radius
t = Bellows thickness
E = Elastic Modulus
v = Poissons Ratio
L = Flexible bellows length
When the expansion joint has a zero length, none of the expansion joint stiffnesses are related. The user must be sure that a
value is entered into all four of the Stiffness fields.
CAESAR II will calculate pressure thrust on the expansion joint if the bellows effective id is given in the expansion joint
auxiliary screen. The mathematical model for pressure thrust applies a force equal to the pressure times the effective area of
the bellows at either end of the expansion joint. The force will tend to open the bellows if the pressure is positive, and close
the bellows if the pressure is negative. Users should note that this model does not exactly distribute the pressure loads
correctly in the vicinity of the expansion joint. In most cases the misapplied load does not affect the solution. There are two
components of the pressure thrust to be applied in practice, rather than the one component applied in the model. The first
component is equal to the pressure times the inside area of the pipe and acts at the first change in direction of the pipe on
either side of the expansion joint. This load will tend to put the pipe wall between the change in direction and the expansion
joint in tension. The second component is equal to the pressure times the difference between the bellows effective area and
inside pipe area. This load acts at the end of the expansion joint and tends to open the bellows up, putting the pipe between
the expansion joint and the change in direction in compression. In the mathematical model the full component of the
pressure thrust force is placed on the ends of the bellows instead of having a portion shifted out on either side of the
expansion joint. A large number of expansion joint examples can be found in Chapter 5 of the Applications Guide.
Chapter 6 Technical Discussions 6-9
Hanger Sizing Algorithm
The basic function of the hanger design algorithm is to calculate the hot load and travel for user-specified hanger locations.
Once the hot load and travel are known, spring tables are entered and the theoretical cold load is calculated for each spring
in the table.
Spring Design Requirements
The smallest single spring that satisfies all design requirements is selected as the designed spring.
The spring design requirements are:
1 Both the hot and the cold loads must be within the spring allowed working range.
2 If the user specified an allowed load variation then the absolute value of the product of the travel and the spring rate
divided by the hot load must be less than the specified variation.
3 If the user specified some minimum available clearance then the spring selected must fit in this space.
If a single spring cannot be found that satisfies the design requirements, CAESAR II will try to find two identical springs that
do satisfy the requirements.
If satisfactory springs cannot be found, CAESAR II recommends a constant effort support for the location.
There are several variations of this approach that arise due to the different design options available in CAESAR II, but for the
most part the general algorithm remains unchanged.
Restrained Weight Case
In any job, if a hanger is to be designed, the first analysis case that must be run is the restrained weight case. This case
usually includes weight, pressure and concentrated loads. Hanger hot loads are calculated in the restrained weight case.
For the restrained weight run, rigid Y restraints are placed at each hanger location, and any anchors to be freed are
properly released. Loads on the Y restraints at hangers, calculated from the restrained weight case, are the hanger hot
design loads.
Operating Case
Immediately after the restrained weight case, an operating analysis is performed. The Y restraints are removed from the
hanger locations and the hot loads just calculated are inserted. Any anchors that were freed for the restrained weight
analysis are fixed.
The operating case vertical displacement at each hanger location defines that hangers travel. If there were single
directional restraints or gaps in the system that changed status in the operating case then the possibility exists that loads on
hangers will be redistributed. When a nonlinear status change is detected CAESAR II reruns the restrained weight case with
the restraints left as they were at the end of the operating case. New restraint loads are calculated and another operating case
is run to get the updated travel.
The operating case must always be the second load case in the set of defined analysis cases.
The user has the ability to define the restrained weight or operating load cases for hanger design any way he sees fit. For
simplicity, CAESAR II recommends the load cases it thinks should be run whenever it detects the first attempt to analyze a
particular system. The user can accept or reject CAESAR IIs recommendations. The user that sets up his own hanger design
load cases should be sure he understands exactly what is done in the restrained weight and operating passes of the hanger
design algorithm.
6-10 Technical Discussions
Installed Load Case
If the user requested the calculation of the actual hanger installed loads, the third analysis level combination case must
define the weight configuration that will exist in the field when the spring is installed. Typically this case includes weight
without fluid contents and concentrated loads.
The theoretical cold, or installed, load is the load on the spring when the pipe has exactly zero displacement. The actual
installed load may differ from the theoretical installed load by (K)(d), where (K) is the spring stiffness and (d) is the
displacement of the pipe in the installed condition. In essence, the actual installed load is calculated by taking the piping
system and freezing all displacements at zero. With the pipe in this condition, the hangers are installed and the theoretical
cold load is applied. The pipe is then defrosted and allowed to adjust its weight position due to the hanger, restraint, and
anchor stiffnesses and the installed hanger loads. Once the system settles out, the total load on each of the hangers is read
and recorded as the actual hanger installed load.
Setting Up the Spring Load Cases
The load cases that must exist for hanger design, as described above, are
Restrained Weight
Operating
Installed Weight ...if the user requested actual hanger installed loads.
After the hanger algorithm has run the load cases it needs to size the hangers. The newly selected springs are inserted into
the piping system and included in the analysis of all remaining load cases.
The spring rate becomes part of the global stiffness matrix, and is therefore added into all subsequent load cases. Hanger
installed loads are concentrated forces and are only included in subsequent load cases that contain the first concentrated
force set, (i.e., +H).
Users may specify any number of their own load cases after the required spring load cases are set up.
Spring hanger design does not affect CAESAR IIs ability to check code compliance. In fact, in CAESAR IIs recommended
load cases, the normal code compliance cases always follow the set of load cases required for hanger design.
Multiple operating case spring hanger design implies that hanger loads and travels from more than one operating case are
included in the spring hanger selection algorithm.
Each spring in a multiple operating case hanger design has a multiple load case design option. This design option tells
CAESAR II how the multiple loads and travels for a single hanger are to be combined to get a single design load and travel.
The set-up of the analysis cases is slightly different for multiple operating case hanger design, and as might be expected, the
difference is that now there is more than one operating case. The actual number of operating cases is specified by the user
on the Hanger Design Control dialog and can be up to 9.
Load cases that must be set up for a multiple load case hanger design that considers two hanger design operating cases are:
Restrained Weight (this doesn't change)
Operating case #1
Operating case #9
Installed Weight ...if the user requested that actual installed loads are to be calculated.
Chapter 6 Technical Discussions 6-11
Constant Effort Support
The specification of the support load for a constant effort hanger completely defines the hanger location. If the user enters
this value it will be included in all hanger design runs and all analysis cases following the hanger cases that include
concentrated loads in their formulation. This value is the load on each support at this location.
Including the Spring Hanger Stiffness in the Design Algorithm
The operating cases for hanger travel are normally analyzed with no stiffness included at the hanger locations (hence these
cases are traditionally referred to as "free thermal" cases). However, when the piping system is very flexible, or the selected
springs are very stiff, the actual resulting spring loads in the hot condition can vary significantly from the theoretically
calculated results. In that case, CAESAR II offers the option to include (via an iterative process) the stiffness of the selected
springs in the operating cases for hanger travel. This can be activated by setting the Hanger Stiffness Load Case option to
"As Designed" for that operating case. (Activating the Configure/Setup option "Include Travel cases to default to "As
Designed".) The user is warned that selection of this option may lead to convergence problems. If this option is used, it is
very important that the hanger load in the cold case (In the physical system) be adjusted to match the reported hanger Cold
Load.
Spring Hanger Hot Loads for as designed springs are always included in all Operating Hanger Travel cases. Cold loads can
be included in subsequent load cases through the use of the H load component. (Note that applying thermal and
displacement effects to the system should make the Cold Load move to the Hot Load in the operating case.)
Other Notes on Hanger Sizing
Users should note that whenever a hanger location is found to hold the pipe down, a beep and a warning message are
flashed to the user. These locations in output are flagged as zero load constant effort supports. These supports are usually
found to be at poor hanger design locations.
Hanger design load cases, unless specifically designed with a "KEEP" status by the user, show up in the output report as
being NOT ACTIVE. Results from these analyses are reflected in the spring hanger table only.
6-12 Technical Discussions
Class 1 Branch Flexibilities
This analytical option was added to CAESAR II for the following reasons:
Automatic local flexibilities at intersections help the user bound the true solution. Because the computer time to do an
analysis is getting less expensive, more frequently an analyst is running several solutions of the same model using
slightly different input techniques to determine the effect of the modeling difference on the results. (This gives the
analyst a degree of confidence in the numbers he is getting.) For example, structural steel supporting structures may be
modeled to see the effect of their stiffnesses, nozzle flexibilities may be added at vessel connections to see how these
features redistribute load throughout the model, friction is added to watch its effect on displacements and equipment
loads, and with CAESAR II users may include Class 1 intersection flexibilities. The characteristic that makes this option
convenient to use is that the user can turn the Class 1 flexibilities on and off via a single parameter in the setup file.
There is no other modification to the input required.
In WRC 329, there are a number of suggestions made to improve the stress calculations at intersections. These
suggestions are fairly substantial, and are given in order of importance. The most important item, as felt by Rodabaugh
in improving the stress calculations at intersections is given, in part, as follows:
In piping system analyses, it may be assumed that the flexibility is represented by a rigid joint at the branch-to-run
centerlines juncture. However, the Code user should be aware that this assumption can be inaccurate and should consider
the use of a more appropriate flexibility representation.
User of the Class 1 branch flexibility feature may be summarized as follows: The user adds the option:
CLASS_1_BRANCH_FLEX to the setup file. This option is a flag, and merely has to appear in the setup file to activate
the option.
Where reduced branch geometry requirements are satisfied, CAESAR II constructs a rigid offset from the centerline of
the header pipe to its surface, and then adds the local flexibility of the header pipe, between the end of the offset, at the
header, and the start of the branch. Stresses computed for the branch, are for the point at its connection with the header.
Where reduced branch geometry requirements are not satisfied, CAESAR II constructs a rigid offset from the centerline
of the header pipe to its surface. The branch piping starts at the end of this rigid offset. There is NO local flexibility due
to the header added. (It is deemed to be insignificant.) Stresses computed for the branch, are for the point at its
connection with the header.
The reduced branch geometry requirements checked by CAESAR II are
d/D s 0.5 and D/T s 100.0
Where:
d = Diameter of branch
D = Diameter of header
T = Wall thickness of header
When the Class 1 branch flexibilities are used, intersection models in the analysis will become stiffer when the reduced
geometry requirements do not apply, and will become more flexible when the reduced geometry requirements do apply.
Stiffer intersections typically carry more load, and thus have higher stresses (lowering the stress in other parts of the system
that have been unloaded). More flexible intersections typically carry less load, and thus have lower stresses, (causing
higher stresses in other parts of the system that have picked up the extra load).
The branch flexibility rules used in CAESAR II are taken from ASME III, Subsection NB, (Class 1), 1992 Edition, Issued
December 31, 1992, from Code Sections NB-3686.4 and NB-3686.5.
Chapter 6 Technical Discussions 6-13
When the reduced branch rules apply, the following equations are used for the local stiffnesses:
TRANSLATIONAL:
AXIAL = RIGID
CIRCUMFERENTIAL = RIGID
LONGITUDINAL = RIGID
ROTATIONAL:
AXIAL = RIGID
CIRCUMFERENTIAL = (kx)d/EI
LONGITUDINAL = (kz)d/EI
Where:
RIGID = 1.0E12 lb./in. or 1.0E12 in.lb./deg.
d = Branch diameter
E = Youngs Modulus
I = Cross Section Moment of Inertia
D = Header diameter
T = Header thickness
T
b
= Branch fitting thickness
kx = 0.1(D/T)
1.5
[(T/t)(d/D)]
0.5
(Tb/T)
kz = 0.2(D/T)[(T/t)(d/D)]
0.5
(Tb/T)
Users are referred to WRC 329 Section 4.9 Flexibility Factors. A brief quote from this section follows:
The significance of k depends upon the specifics of the piping system. Qualitatively, if k is small compared to the
length of the piping system, including the effect of elbows and their k-factors, then the inclusion of k for branch
connections will have only minor effects on the calculated moments. Conversely, if k is large compared to the piping
system length, then the inclusion of k for branch connections will have major effects. The largest effect will be to greatly
reduce the magnitude of the calculated moments acting on the branch connection. To illustrate the potential significance of
ks for branch connections, we use the equation [above] to calculate k for a branch connection with D=30 in.,
d=12.75 in. T=t=0.375 in.:
k = 0.1(80)
1.5
(0.425)
0.5
* (1.0) = 46.6
This compares to the more typical rigid-joint interpretation that k=1, rather than k=46.6 !
Further discussion in section 4.9 illustrates additional problems that can arise by overestimating the stiffness at branch
connections. Problems arise by believing mistakenly that the stress at the intersection is too high. Further reference should
be made to this section in WRC 329.
The branch automatic flexibility generation can be used where the user has only defined the branch element in the model,
i.e. has left the header piping out of the analysis. In this case there will be no offset equal to one-half of the header
diameter applied to the branch end. A partial intersection is one where either the header pipe is not modeled, is modeled
with a single element, or is part of a geometric intersection where the header pipes are not colinear. In the case where there
is no header pipe going to the intersection there will be no modification to the model for the class 1 branch flexibilities.
When at least a single header pipe is recognized, the local flexibility directions are defined by the branch alone and in
accordance with the CAESAR II defaults for circumferential and longitudinal directions for the branch and header. Users are
6-14 Technical Discussions
recommended to build full intersection models at all times (not only when employing the class 1 branch flexibility.) In most
cases building full intersection models will eliminate problems caused by the assumptions necessary when a partial
intersection is described.
In the equations in NB-3686.5 for tn, the thickness of the branch pipe is used in all cases.
When branches are skewed with respect to the header pipe, and where the two header pipes are colinear, the local Class 1
flexibilities are still taken to be the longitudinal and circumferential directions that are tangent to the header surface at its
intersection with the branch.
Class 1 branch flexibilities can be formed at both ends of a single pipe element.
Note: The offsets necessary to form the class 1 intersections are automatically generated by CAESAR II. There is no extra
input required by the user to have CAESAR II build these intersections.
(If there are already user-defined offsets at an intersection end, the computed offset to get from the header centerline to its
surface along the centerline of the branch will be added to the already entered user offset.) Automatic offsets will be
generated providing that the distance from the header centerline to the header surface along the branch centerline is less than
or equal to 98% of the total pipe straight length.
When a bend curved element is part of an intersection model, the offset and flexibility calculations will not be performed.
Chapter 6 Technical Discussions 6-15
Modeling Friction Effects
There are two approaches to solving the friction problem; insert a force at the node which must be over come for motion to
occur, or insert a stiffness which applies an increasing force up to the value of Mu * Normal force. CAESAR II uses the
restraint stiffness method. (An excellent paper on this subject is Inclusion of a Support Friction Into a Computerized
Solution of a Self-Compensating Pipeline by J. Sobieszczanski, published in the Transactions of the ASME, Journal of
Engineering for Industry, August 1972. A summary of the major points of this paper can be found below.)
Ideally, if there is motion at the node in question, the friction force is equal to (Mu * Normal force). However, since we
have a non-rigid stiffness at that location to resist the initial motion, the node can experience displacements. The force at the
node will be the product of the displacement and the stiffness. If this resultant force is less than the maximum friction
force (Mu * Normal force), the node is assumed to be not sliding, even though we see displacements in the output
report.
The maximum value of the force at the node is the friction force, Mu * Normal force. Once this value is reached, the
reaction at the node stops increasing. This constant force value is then applied to the global load vector during the next
iteration to determine the nodal displacements. Basically here is what happens in a friction problem.
1 The default friction stiffness is 1,000,000 lb./in. This value should be decreased to improve convergence.
2 Until the horizontal force at the node equals Mu * Normal force, the restraint load is the displacement times the friction
stiffness.
3 Once the maximum value of the friction force is reached, the friction force will stop increasing, since a constant effort
force is inserted.
By increasing the friction stiffness in the setup file, the displacements at the node will decrease to some degree. This may
cause a re-distribution of the loads throughout the system. However, this could have adverse affects on the solution
convergence.
If problems arise during the solution of a job with friction at supports, reducing the friction stiffness will usually improve
convergence. Several runs should be made with varying values of the friction stiffness to insure the system behavior is
consistent.
Summary of J. Sobieszczanskis ASME Paper
For dry friction, the friction force magnitude is a step function of displacement. This discontinuity determines the
problem as intrinsically nonlinear and eliminates the possibility of using the superposition principle.
The friction loading on the pipe can be represented by an ordinary differential equation of the fourth order with a
variable coefficient that is a nonlinear function of both dependent and independent variables. No solution in closed form
is known for an equation of this type. Solution has to be sought by means of numerical integration to be carried out
specifically for a particular pipeline configuration.
Dry friction can be idealized by a fictitious elastic foundation, discretized to a set of elastic (spring) supports.
A well-known property of an elastic system with dry friction constraints is that it may attain several static equilibrium
positions within limits determined by the friction forces.
THE WHOLE PROBLEM THEN HAS CLEARLY NOT A DETERMINISTIC, BUT A STOCHASTIC
CHARACTER.
6-16 Technical Discussions
Nonlinear Code Compliance
Nonlinear piping code compliance can be directly satisfied by
1 Performing an operating and sustained analysis of the system including in each case the effect of nonlinear restraints.
2 Subtracting the sustained case displacements from the operating case displacements to find the displacement range.
3 Calculating the expansion stresses from the displacement range solved for in #2 above.
Approximate approaches usually involve some combination of the above. The approximate combination used depends
typically on the inherent limitations of the base program. In several commonly used programs, the approach taken is
1 Formulate and solve for operating case displacements including an iteration to deal with the effect of nonlinear
restraints in the system.
2 Run the thermal-only analysis of the system to calculate expansion stresses with restraints in the same condition as they
were at the end of #1.
3 Run the weight+pressure only analysis of the system to calculate sustained stresses, again with restraints in the same
condition as they were at the end of #1.
This alternate approach is identical to the first method only when the sustained analysis final stiffness matrix is the same as
the operating analysis final stiffness matrix. The resulting error in the displacement range can be found from
{[F
o
] - [F
s
]}f
s
.
Where:
[F
o
] - is the operating analysis final flexibility matrix (i.e. the inverse of the stiffness matrix).
[F
s
] - is the sustained analysis final flexibility matrix.
f
s
- is the sustained analysis load vector.
CAESAR II uses the exact method described above for calculating the expansion stress range. In addition CAESAR II scans the
users input and recommends loading cases and combinations for performing the operating, sustained and expansion stress
calculations. This recommendation can prove very useful when performing spring hanger analysis of a multiple operating
case system.
Chapter 6 Technical Discussions 6-17
Sustained Stresses and Nonlinear Restraints
The proper computation of sustained stresses has been an issue since the late 1970s, when computerized pipe stress analysis
programs first attempted to address the problem of non-linear restraints. The existing piping codes offered little guidance on
the subject, since their criteria were developed during the era when all analyses were considered to behave in a strictly linear
fashion. The problem arises because the codes require that a piping system be analyzed separately for sustained loadings
the engineer must determine which stresses are caused by which loadings. Sustained loads are force loadings which are
assumed not to change, while expansion loadings are displacement loadings which vary with the system operating
conditions. Determination of the sustained loads is the simple part most everybody agrees that those forces consist of
weight, pressure, and spring preloads these forces remain relatively constant as the piping system goes through its
thermal growth. However, confusion occurs when the status of nonlinear restraints change (pipes lift off of supports, gaps
close, etc.) as the pipe goes from its hot to cold state in this case, which boundary conditions should be used when
evaluating the applied forces? Or in other words, what portion of the stress in the operating case is caused by weight loads,
and what portion is caused by expansion effects? (Note that there is no corresponding confusion on the question of
calculating expansion stresses, since the codes are explicit in their instructions that the expansion stress range is the
difference between the operating and cold stress distributions, both of which are known.)
The obvious answer to this question, to the developers of some pipe stress programs, was that the sustained stress
calculation should be done using the operating, or hot boundary condition. This compounded the problem, in that the laws
of superposition no longer held in other words, the results of sustained (W+P) and thermal (T) cases, when added
together, did not equal the results of the operating (W+P+T) case! One pioneering program, DYNAFLEX, attempted to
resolve this by introducing the concept of the thermal component of weight an oxymoron, in our opinion. Other
programs, notably those which came from the mainframe/linear analysis world, had to approximate the behavior of these
non-linear restraints. Their approach to the problem is to run an operating case, obtain the restraint status, and modify the
model according to these results. All subsequent load cases analyzed use this restraint configuration. The fact that the laws
of static superposition didn't hold was hopefully not noticed by the user. CAESAR II, on the other hand, represents new
technology, developed expressly for operation on the PC, and therefore incorporates directly the effects of non-linear
restraints. This is done by considering each load case independently the restraint configuration is determined for each
load case by the program as it runs, based upon the actual loads which are considered to be present.
Some users have asserted that there are actually two sustained load cases. In fact, there has been a B31.3 code interpretation
that indicates that the sustained stress may also be checked with the operating restraint configuration. Calculating the
sustained stresses using the operating restraint status raises several other issues; what modulus of elasticity should be used,
and which sustained stresses should be used for occasional cases.
It is COADEs assertion that there is only one sustained case (otherwise it is not sustained) there can be, however,
multiple sustained stress distributions. The two most apparent are those associated with the cold (installed) and hot
(operating) configurations, however, there are also numerous in-between, as the piping system load steps from cold to hot.
Whether the true sustained load case occurs during the installed or operating case is a matter of the frame of reference. If
an engineer first sees a system in its cold condition, and watches it expand to its operating condition, it appears that the first
case (since weight and pressure primary loads are present) is the sustained case, and the changes he viewed are
thermal effects (due to heat up) secondary loads due to displacements. If a second engineer first sees the same system in
the operating case and watches it cool down to the cold case, he may believe that the first case he saw (the operating case) is
the sustained case, and changes experienced from hot to cold are the thermal expansion effects (the thermal stress ranges are
the same in both cases). Consider the further implications of cryogenic systems where changes from installed to
operating are the same as those experienced by hot systems when going from operating to installed. Once elastic shakedown
has occurred, the question becomes clouded even further, due to the presence of thermally induced pre-stresses in the pipe
during both the cold and hot conditions. We feel either the operating or installed case (or some other one in-between) could
justifiably be selected for analysis as the sustained case, as long as the program is consistent.
We have selected the installed case (less the effect of cold spring) as our reference sustained case, since thermal effects can
be completely omitted from the solution (as intended by the code), and this best represents the support configuration when
the sustained loads are initially applied. If the pipe lifts off of a support when going from installed to operating, we view this
as a thermal effect consistent with the piping codes view of thermal effects as the variation of stress distribution as the
6-18 Technical Discussions
piping system goes from cold to hot (this view is explicitly corroborated by one code the French petrochemical code,
which states that weight stress distributions due to thermal growth of the pipe should be considered as expansion stresses).
For example, we feel that a change in a rigid support load from 2,000 lbs to zero should be treated no differently than would
be a variable spring load changing from 6,000 lbs to 4,000 lbs (or another rigid support load going 2,000 lbs to 1 lb). In the
former case, if the pipe became overstressed, it would yield, and sag back to the support, relieving the stress. This process
is identical to the way that all other expansion stresses are relieved in a piping system.
We are confident that our interpretation is correct. However, we understand that our users may not always agree with us
that is why CAESAR II provides the greatest ability to custom tailor the analysis to ones individual specifications. If desired,
a hot sustained case can be analyzed by adding two load cases to those normally recommended by CAESAR II. This would
be done by assuming that the pipe expands first, and then the sustained loads are applied (this is of course an idealized
concept, but the stresses can only be segregated by segregating the applied loads, so the sustained loads can only be applied
either before, or after, the expansion loads). Following are the default load cases, as well as those required for a hot
sustained.
Default New
W+P1+T1(OPE) W+P1+T1(OPE)
W+P1(SUS) W+P1(SUS)
L1-L2(EXP) T1 (EXP)
L1-L2(EXP)
L1-L3(SUS)
In the new load case list, the second case still represents the cold sustained, while the fourth case represents the expansion
case (note that L1-L2, or W+P1+T1-W-P1, equals T1, with non-linear effects taken into account). The third case represents
the thermal growth of the weightless, non-pressurized pipe, against the non-linear restraints.
The fifth case (L1-L3, or W+P1+T1-T1, equals W+P1) represents the application of weight and pressure to that expanded
case, or the hot sustained case. Note that when the piping system is analyzed as above, the actual effects of the non-linear
restraints are considered (they are not arbitrarily removed from the model), and the laws of superposition still hold.
An alternative school of thought believes that a "hot sustained" is only valid if (1) the sustained, primary loads are applied,
(2) all springs are showing their Hot Load settings, and (3) any supports that lift off (or otherwise become non-active) have
been removed from the model. An analysis such as this is achievable by setting the "Keep/Discard" status of the Restrained
Weight case (the first hanger design load case) to "Keep", thus permitting the results of that case to be viewable as for any
other load case. The Restrained Weight case automatically removes restraints that become non-active during the designated
operating case, and apply the Hot Load at each of the hanger locations.
Notes on Occasional Load Cases
Several piping codes require that the stresses from occasional loads (such as wind or earthquake) be added to the sustained
stresses (due to weight, pressure, and other constant loads) before comparing them to their allowables. This combination is
easily created in CAESAR II:
CASE #
1. W+P+F1 (SUS): Sustained stresses
2. WIND (OCC): Wind load set
3. U1 (OCC): Uniform (g) load set for earthquake
4. L1+L2 (OCC): Code stresses for wind *
5. L1+L3 (OCC): Code stresses for earthquake*
* Scalar Summation Method required
Chapter 6 Technical Discussions 6-19
If nonlinear effects are modeled in the system these combinations may not be so straight forward. Friction, one-direction
restraints and double-acting restraints with gaps are the nonlinear items which present this complication. Wind loading on a
long vertical run of pipe with a guide will serve as an example. Assume there is a one inch gap between the pipe and guide.
Under normal operation, the pipe moves 3/4 inch towards the stop leaving a gap of 1-3/4 inch on either side of the pipe and
a 1/4 inch gap on the other side. If wind loads are analyzed alone, the pipe is allowed to move 1 inch from its center point in
the guide to the guide stop. Since occasional loads are usually analyzed with the system in operation, the pipe may be
limited to a 1/4 inch motion as the gap is closed in one direction, and 1-3/4 inch if the gap is closed in the opposite direction.
With nonlinear effects modeled in the system, the occasional deflections (and stresses) are influenced by the operating
position of the piping.
The following list of CAESAR II load cases takes this point into consideration. Note that the load cases shown below are only
for wind acting in one direction, i.e., +X. Depending on the system, the most critical loads could occur in any direction, i.e.,
+/-X, +/-Z or skewed in an XZ direction.
The intention of the following load case construction is to find the occasional loads effect on the piping system in the
operating condition. The stress due to the moment change from the operating to the operating plus wind case is added to the
stress from the sustained case.
The isolated wind effect on the piping system in the operating condition in is computed in Case 5. Case 6 adds the stresses
from Case 5 to the sustained stresses from Case 2.
CASE #
1. W+T+P (OPE): Operation analysis
2. W+P (SUS): Sustained stresses
3. W+T+P+WIND (OPE): Operating analysis with wind
4. L1-L2 (EXP): Expansion stresses (Algebraic summation)
5. L3-L1 (OCC): Winds net deflection (Algebraic summation)
6. L2+L5 (OCC): Code stresses for wind (Scalar summation)
6-20 Technical Discussions
Static Seismic Loads
Static earthquake loads are applied in a manner very similar to static wind loads. The static loading magnitude is considered
to be in direct proportion to the elements weight. Earthquake load magnitudes are given in terms of the gravitational
acceleration constant, i.e. g's. If an earthquake is modeled as having a 0.5-g load in the X direction, then half of the systems
weight is turned into a uniform load and applied in the X direction.
Earthquake static load cases are set up exactly as they are for wind occasional loads, i.e. the same load case, nonlinearity,
and directional sensitivity logic. In some cases the client specifies the magnitude of the earthquake loading in g's and the
direction(s). In others, the analysis is left to the sole discretion of the analyst. It is not unusual to see only X or X-Y
components of an earthquake. It is not uncommon to see Y only components, or X, Y, and Z simultaneous components.
Dynamic earthquakes are discussed later in this chapter, in the dynamic analysis and output chapters, and in the screen
reference chapter. The ASCE #7 method for determining earthquake coefficients is described below. Once calculated, the
g-factors should be entered as uniform loads on the piping spreadsheet.
Note: The Uniform Load in G's (on page 3-121) check box must also be enabled in the spreadsheet special execution
parameters.
The total lateral force at the base of a structure is to be computed from:
V = ZIKCSW
Where:
V - total lateral force or shear at the base
Znumerical coefficient from table 22
Knumerical coefficient from table 23
Cnumerical coefficient from Sect. 9.4
Ssoil factor from table 25
Wtotal dead load
The g-factor can be found by dividing Eq. 6 through by W.
gs = V/W = ZIKCS
The product CS does not need to exceed the value 0.14. Use this value as a conservative maximum.
The following table provides the seismic zone coefficient (Z)
Seismic Zone
Coefficient, Z
4 1
3 3/4
2 3/8
1 3/16
0 1/8
From the following table, the importance factor can be found: (However use a value for I = 1.0. The categories in this table
are identical for those used in the wind load calculation.)
Chapter 6 Technical Discussions 6-21
Category Number
I 1
II 1025
III 1.5
IV N/A
The following table shows K varying from 0.67 to 2.0. Use K=2.0 for Structures other than buildings.
So the equation for the g load:
g = ZIKCS
reduces to:
g = Z (1.0) (2.0) (0.14)
and for the various value of Z:
Seismic Zone Product "g" Load
4 (1)(1)(2)(0.14) 0.28
3 (3/4)(1)(2)(0.14) 0.21
2 (3/8)(1)(2)(0.14) 0.105
1 (3/16)(1)(2)(0.14) 0.0525
0 (1/8)(1)(2)(0.14) 0.035
ASCE #7 - 1990 is the 1990 revision to ANSI A58.1 1982. There are no revisions to this code which affect CAESAR II.
ASCE #7 - 1993 has completely changed the approach for "static" seismic analysis. These changes are not addressed by
this discussion.
6-22 Technical Discussions
Wind Loads
Currently CAESAR II enables users to access the wind load data from ten different wind codes.
AS/NZ 1170:2002 IBC 2006
Brazil NBR 6123 IS 875
BS6399-97 Mexico 1993
China GB 50009 NBC 2005
EN 2005 UBC
Wind loads are generated by multiplying the pipe exposed area, including insulation, and considering the angle to the wind,
by the equivalent wind pressure and the pipe shape factor. There are typically three different ways to get the equivalent
wind pressure:
ASCE #7 (1995)
Pressure vs. elevation table entry
Velocity vs. elevation table entry
The total wind force on the element is calculated from the equation below
F = P
eq
SA
Where:
F = the total wind force on the element
P
eq
= the equivalent wind pressure (dynamic
pressure)
S = the pipe element wind shape factor
A = the pipe element exposed area as shown in the
figure to the right.
P
eq
is calculated for each end of the element and the average taken. The average applies uniformly over the whole length of
the element. Note, the wind force is applied in the three global directions as a function of the element direction cosines.
If the user enters a velocity vs. elevation table then the velocity is converted to a dynamic pressure using the following
equation:
P = 1/2 V
2
Where V is the wind velocity and is the air density.
The WIND SHAPE FACTOR is entered on the pipe spreadsheet and, for cylindrical elements, the value from Table 12 is
between 0.5 and 0.7. A value of 0.65 is typical. The wind shape factor as entered is distributive. This means that the
shape factor applies for all following elements until zeroed or changed.
Important: Users do not have to enter the shape factor on each pipe spreadsheet. Zero (or turn "Off") the wind shape factor
if the piping system runs inside of a building or similarly protective structure.
Chapter 6 Technical Discussions 6-23
Wind load data is entered on the Wind Loads (on page 3-63) tab of the Static Load Case Builder. Up to four different
wind loads can be entered per analysis. These typically might be setup to model wind loads in the +X, -Y, and -Z directions.
The ASCE #7 ( 1995) Method for computing equivalent pressure requires several computerized table look ups and
interpolation. The user enters the following parameters:
1 Basic wind speed (mph) - The minimum allowed basic wind speed is 85 mph. This does not include averages for
abnormally high wind loading events such as hurricanes or tornadoes.
ASCE #7 refers to fig. 6-1 for basic wind speeds in the continental United States. The following description is a crude
representation of Figure 1:
California 85 mph (124.6 ft/sec)
Other West Coast Areas 85 mph (124.6 ft/sec)
Great Plains 90 mph (132.0 ft/sec)
Non-Coastal Eastern United States 90 mph (132.0 ft/sec)
Gulf Coast 130 mph (190.6 ft/sec)
Florida Carolinas 130 mph (190.6 ft/sec)
Miami 145 mph (212.6 ft/sec)
New England Coastal Areas 120 mph (176.0 ft/sec)
2 Wind Exposure Options
Large oily center
Urban, suburban, and wooded areas
Open terrain
Flat coastal areas
3 Structural Classification Options
Everything except the following options (used most often)
Primary occupancy more than 100 people
Essential facilities, i.e. hospitals
Failure represents low hazard
4 Topographic Factor Parameters (sec. 6.5.5)
Height of hill or escarpment
Crest distance
Height above ground level
Distance from crest to site
Hill type
6-24 Technical Discussions
The following procedure from the appendix is used to calculate the effective wind pressure:
1 Get the Importance Factor from Table 6-2 (p.17).
2 Get (Alpha), Zg, from Table C 6-2.
3 Calculate Kz from Eq. C2 (p.152).
4 Calculate Kzt from Eq. 6-2 (p.34).
5 Calculate qz from Eq. 6-1 (p.17)
6 Calculate Gz from sec 6.6.
7 Calculate the effective wind pressure from:
PRESSURE = Gz * qz * Shape Factor
Note: Winds of 20 to 40 mph can cause vortex shedding and excitation in the 30 Hz and higher range that can cause
fatigue failure in smaller line sizes particularly susceptible to fatigue type failures. To analyze vortex shedding, use an
harmonic analysis method.
Elevation
The accurate elevation of each individual piping element may, or may not be important depending on the total height,
diameter and rigidity of the piping system and attachments. By default, CAESAR II starts the first node on the first element at
an elevation of 0.0. If this is not close enough to the true elevation then the user should set the true coordinates of the piping
system through the command EDIT - GLOBAL. This presents a dialog requesting coordinates for the first node of any
disconnected section. The coordinates for up to 100 node points can be specified and saved as part of the input data from the
model.
Chapter 6 Technical Discussions 6-25
Hydrodynamic (Wave and Current) Loading
Ocean waves are generated by wind and propagate out of the generating area. The generation of ocean waves is dependent
on the wind speed, the duration of the wind, the water depth, and the distance over which the wind blows is referred to as
the fetch length. There a variety of two dimensional wave theories proposed by various researchers, but the three most
widely used are the Airy (linear) wave theory, Stokes 5
th
Order wave theory, and Dean's Stream Function wave theory. The
later two theories are non-linear wave theories and provide a better description of the near surface effects of the wave.
(The term two dimensional refers to the uni-directional wave. One dimension is the direction the wave travels, and the other
dimension is vertical through the water column. Two dimensional waves are not found in the marine environment, but are
somewhat easy to define and determine properties for, in a deterministic sense. In actuality, waves undergo spreading, in the
third dimension. This can be easily understood by visualizing a stone dropped in a pond. As the wave spread, the diameter
of the circle increases. In addition to wave spreading, a real sea state includes waves of various periods, heights, and
lengths. In order to address these actual conditions, a deterministic approach cannot be used. Instead, a sea spectrum is
utilized, which may also include a spreading function. As there are various wave theories, there are various sea spectra
definitions. The definition and implementation of sea spectra are usually employed in dynamic analysis. Sea Spectra and
dynamic analysis will not be discussed in this article.)
The linear or Airy wave theory assumes the free surface is symmetric about the mean water level. Furthermore, the water
particle motion is a closed circular orbit, the diameter of which decays with depth. (The term circular should be taken
loosely here, the orbit varies from circular to elliptical based on whether the wave is in shallow or deep water.) Additionally,
for shallow water waves, the wave height to depth ratio (H/D) is limited to 0.78 to avoid breaking. (None of the wave
theories address breaking waves!) The figure below shows a typical wave and associated hydrodynamic parameters.
SWL - The still water level.
L - The wave length, the horizontal distance between successive crests or troughs.
H - The wave height, the vertical distance between the crest and trough.
D - The water depth, the vertical distance from the bottom to the still water level.
q - The surface elevation measured from the still water level.
Ocean Wave Particulars
The Airy Wave theory provides a good first approximation to the water particle behavior. The nonlinear theories provide a
better description of particle motion, over a wider range depths and wave heights. Stokes 5
th
Wave theory is based on a
power series. This wave theory does not apply the symmetric free surface restriction. Additionally, the particle paths are no
longer closed orbits, which mean there is a gradual drift of the fluid particles, i.e. a mass transport.
Stokes 5
tH
Order Wave Theory however, does not adequately address steeper waves over a complete range of depths.
Deans Stream Function wave theory attempts to address this deficiency. This wave theory employs an iterative numerical
technique to solve the stream function equation. The stream function describes not only the geometry of a two dimensional
flow, but also the components of the velocity vector at any point, and the flow rate between any two streamlines.
6-26 Technical Discussions
The most suitable wave theory is dependent on the wave height, the wave period, and the water depth. Based on these
parameters, the applicable wave theory can be determined from the figure below (from API-RP2A, American Petroleum
Institute - Recommended Practice 2A).
Applicable Wave Theory Determination
The limiting wave steepness for most deep water waves is usually determined by the Miche Limit:
H / L = 0.142 tanh( kd )
Where:
H is the wave height
L is the wave length
k is the wave number (2t)/L
d is the water depth
Pseudo-Static Hydrodynamic Loading
CAESAR II allows individual pipe elements to experience loading due to hydrodynamic effects. These fluid effects can
impose a substantial load on the piping elements in a manner similar to, but more complex than wind loading.
The various wave theories incorporated into CAESAR II as well as the various types of current profiles are discussed below.
The wave theories and the current profile are used to compute the water particle velocities and accelerations at the node
points. Once these parameters are available, the force on the element can be computed using Morrisons equation:
F = 1/2 * * C
d
* D * U * |U| + t/4 * * C
m
* D
2
* A
Chapter 6 Technical Discussions 6-27
Where
- is the fluid density
C
d
- is the drag coefficient
D - is the pipe diameter
U - is the particle velocity
C
m
- is the inertial coefficient
A - is the particle acceleration
The particle velocities and accelerations are vector quantities which include the effects of any applied waves or currents. In
addition to the force imposed by Morrisons equation, piping elements are also subjected to a lift force and a buoyancy
force. The lift force is defined as the force acting normal to the plane formed by the velocity vector and the elements axis.
The lift force is defined as:
Fl = 1/2 * * C
l
* D * U
2
Where
- is the fluid density
Cl - is the lift coefficient
D - is the pipe diameter
U - is the particle velocity
The buoyancy force acts upward, and is equal to the weight of the fluid volume displaced by the element.
Once the force on a particular element is available, it is placed in the system load vector just as any other load is. A standard
solution is performed on the system of equations which describe the piping system. (The piping system can be described by
the standard finite element equation:
[K] {x} = {f}
Where
[K] - is the global stiffness matrix for the entire system
{x} - is the displacement / rotation vector to solve for
{f} - is global load vector
The element loads generated by the hydrodynamic effects are placed in their proper locations in {f}, similar to weight,
pressure, and temperature. Once [K] and {f} are finalized, a standard finite element solution is performed on this system of
equations. The resulting displacement vector {x} is then used to compute element forces, and these forces are then used to
compute the element stresses.)
Except for the buoyancy force, all other hydrodynamic forces acting on the element are a function of the particle velocities
and accelerations.
AIRY Wave Theory Implementation
Airy Wave theory is also known as Linear Wave theory, due to the assumption that the wave profile is symmetric about
the mean water level. Standard Airy Wave theory allows for the computation of the water particle velocities and
accelerations between the mean surface elevation and the bottom. The Modified Airy Wave theory allows for the
consideration of the actual free surface elevation in the computation of the particle data. CAESAR II includes both the
standard and modified forms of the Airy wave theory.
6-28 Technical Discussions
To apply the Airy Wave theory, several descriptive parameters about the wave must be given. These values are then used to
solve for the wave length, which is a characteristic parameter of each unique wave. CAESAR II uses Newton-Raphston
iteration to determine the wave length by solving the dispersion relation, shown below:
L = (gT
2
/ 2t) * tanh(2tD / L)
Where
g - is the acceleration of gravity
T - is the wave period
D - is the mean water depth
L - is the wave length to be solved for
Once the wave length (L) is known, the other wave particulars of interest may be easily determined. The parameters
determined and used by CAESAR II are: the horizontal and vertical particle velocities ( UX and UY ), the horizontal and
vertical particle acceleration ( AX and AY ), and the surface elevation above (or below) the mean water level ( ETA ). The
equations for these parameters can be found in any standard text (such as those listed at the end of this section) which
discusses ocean wave theories, and therefore will not be repeated here.
STOKES Wave Theory Implementation
The Stokes Wave is a 5th order gravity wave, and hence non-linear in nature. The solution technique employed by CAESAR
II is described in a paper published by Skjelbreia and Hendrickson of the National Engineering Science Company of
Pasadena California in 1960. The standard formulation as well as a modified formulation (to the free surface) is available in
the CAESAR II Stokes 5th Order Wave Theory.
The solution follows a procedure very similar to that used in the Airy wave, characteristic parameters of the wave are
determined by using Newton-Raphston iteration, followed by the determination of the water particle values of interest.
The Newton-Raphston iteration procedure solves two non-linear equations for the constants beta and lambda. Once these
values are available, the other twenty constants can be computed. After all of the constants are known, CAESAR II can
compute: the horizontal and vertical particle velocities ( UX and UY ), the horizontal and vertical particle acceleration ( AX
and AY ), and the surface elevation above the mean water level (ETA).
Stream Function Wave Theory Implementation
In addition to the forces imposed by ocean waves, piping elements may also be subjected to forces imposed by ocean
currents. There are three different ocean current models in CAESAR II; linear, piece-wise, and a power law profile.
The linear current profile assumes that the current velocity through the water column varies linearly from the specified
surface velocity (at the surface) to zero (at the bottom). The piece-wise linear profile employs linear interpolation between
specific depth/velocity points specified by the user. The power law profile decays the surface velocity to the 1/7 power.
While waves produce unsteady flow, where the particle velocities and accelerations at a point constantly change, current
produces a steady, non-varying flow.
Ocean Currents
In addition to forces imposed by ocean waves, piping elements may also be subjected to forces imposed by ocean currents.
There are three different ocean current models in CAESAR II; linear piece-wise linear profile, and a power law profile. The
linear current profile assumes that the current velocity though the water column varies linearly from the specified surface
velocity (at the surface to zero (at the bottom). The piece-wise linear profile employs linear interpolation between specific
"depth /velocity" points specified by the user. The power law profile decays the surface velocity to the 1/7 power.
Chapter 6 Technical Discussions 6-29
While waves produce unsteady flow, where the particle velocities and accelerations at a point constantly change, current
produces a steady, non-varying flow.
Technical Notes on CAESAR II Hydrodynamic Loading
The input parameters necessary to define the fluid loading are described in detail in the next section. The basic parameters
describe the wave height and period, and the current velocity. The most difficult to obtain, and also the most important
parameters, are the drag, inertia, and lift coefficients, C
d
, C
m
, and C
l
. Based on the recommendations of API RP2A and
DNV (Det Norske Veritas), values for C
d
range from 0.6 to 1.2, values for C
m
range from 1.5 to 2.0. Values for Cl show a
wide range of scatter, but the approximate mean value is 0.7.
The inertia coefficient C
m
is equal to one plus the added mass coefficient C
a
. This added mass value accounts for the mass
of the fluid assumed to be entrained with the piping element.
In actuality, these coefficients are a function of the fluid particle velocity, which varies over the water column. In general
practice, two dimensionless parameters are computed which are used to obtain the Cd, Cm, and Cl values from published
charts. The first dimensionless parameter is the Keulegan-Carpenter Number, K. K is defined as:
K = U
m
* T / D
Where:
U
m
- is the maximum fluid particle velocity
T - is the wave period
D - is the characteristic diameter of the element.
The second dimensionless parameter is the Reynolds number, R
e
. R
e
is defined as
R
e
= U
m
* D / v
Where:
U
m
- is the maximum fluid particle velocity
D - is the characteristic diameter of the element.
v - is the kinematic viscosity of the fluid (1.26e-5 ft
2
/sec for sea water).
Once K and R
e
are available, charts are used to obtain C
d
, C
m
, and C
l
. (See Mechanics of Wave Forces on Offshore
Structures by T. Sarpkaya, Figures 3.21, 3.22, and 3.25 for example charts, which are shown in the figures below.)
6-30 Technical Discussions
Chapter 6 Technical Discussions 6-31
In order to determine these coefficients, the fluid particle velocity (at the location of interest) must be determined. The
appropriate wave theory is solved, and these particle velocities are readily obtained.
Of the wave theories discussed, the modified Airy and Stokes 5
th
theories include a modification of the depth-decay
function. The standard theories use a depth-decay function equal to cosh(kz) / sinh(kd),
Where:
k - is the wave number, 2t /L
L - is the wave length
d - is the water depth
z - is the elevation in the water column where the data is to be determined
The modified theories include an additional term in the numerator of this depth-decay function. The modified depth-decay
function is equal to cosh(od) / sinh(kd),
Where:
o - is equal to z / (d + q)
The term od represents the effective height of the point at which the particle velocity and acceleration are to be computed.
The use of this term keeps the effective height below the still water level. This means that the velocity and acceleration
computed are convergent for actual heights above the still water level.
As previously stated, the drag, inertia, and lift coefficients are a function of the fluid velocity and the diameter of the
element in question. Note that the fluid particle velocities vary with both depth and position in the wave train (as determined
by the applied wave theory). Therefore, these coefficients are in fact not constants. However, from a practical engineering
point of view, varying these coefficients as a function of location in the Fluid field is usually not implemented. This
practice can be justified when one considers the inaccuracies involved in specifying the instantaneous wave height and
period. According to Sarpkaya, these values are insufficient to accurately predict wave forces, a consideration of the
previous fluid particle history is necessary. In light of these uncertainties, constant values for C
d
, C
m
, and C
l
are
recommended by API and many other references.
The effects of marine growth must also be considered. Marine growth has the following effects on the system loading: the
increased pipe diameters increase the hydrodynamic loading; the increased roughness causes an increase in C
d
, and
therefore the hydrodynamic loading; the increase in mass and added mass cause reduced natural frequencies and increase
the dynamic amplification factor; it causes an increase in the structural weight; and possibly causes hydrodynamic
instabilities, such as vortex shedding.
Finally, Morrisons force equation is based the small body assumption. The term small refers to the diameter to wave
length ratio. If this ratio exceeds 0.2, the inertial force is no longer in phase with the acceleration of the fluid particles and
diffraction effects must be considered. In such cases, the fluid loading as typically implemented by CAESAR II is no longer
applicable.
Additional discussions on hydrodynamic loads and wave theories can be found in the references at the end of this article.
6-32 Technical Discussions
Input: Specifying Hydrodynamic Parameters in CAESAR II
The hydrodynamic load analysis requires the specification of several measurable parameters which quantify the physical
aspects of the environmental phenomenon in question.
Note: Users can enter four different wave loads here. Use the Editing Load Case buttons to move up or down between the
Wave Load Input Spreadsheets.
The necessary hydrodynamic parameters are discussed in the following paragraphs and a CAESAR II hydrodynamic loading
dialog is shown in the figure below.
Wave Loading Editing in the Load Case Editor
Current Data
Profile TypeThis entry defines the interpolation method used by CAESAR II to determine the current velocity as a function
of depth. Available options for this entry are: a power law profile, a piece-wise linear profile, and a linear profile.
The power law profile determines the current velocity at depth D according to the equation:
V
d
= V
s
* [d
i
/ D]
p
Where
V
d
- is the velocity at depth d
i
V
s
- is the specified velocity at the surface
D - is the water depth
p - is the power, set to 1/7
Chapter 6 Technical Discussions 6-33
The piece-wise linear profile performs a linear interpolation of a velocity verse depth table (provided by the user) to obtain
the current velocity at depth d
i
. When this type profile is specified, a table of depths and velocities must be provided. The
table should start at the surface (a depth of zero) and progress in the direction of increasing depth, to the sea bed.
The linear profile also performs a linear interpolation to obtain the current velocity at depth d
i
. However, this method
assumes the current velocity varies linearly from the specified surface velocity to zero at the sea bed.
Current Speed This entry defines the current speed at the surface. The units for this entry are (length/time) as defined
by the active units file at the time of input. This value should always be a positive entry.
Current Direction Cosines These entries define the direction of fluid transport due to the current. These fields are
unitless, and follow the standard software global axis convention.
Wave Data
Wave Theory Indicator This entry specifies which wave theory is to be used to compute the water particle velocities
and accelerations. The wave theories presently available are:
Standard Airy Wave This is also known as linear wave theory. Discussion of this theory can be found in the previously
mentioned references.
Modified Airy Wave This is a modification of the standard Airy theory which includes the free surface effects due to
the wave. The modification consists of determining a depth scaling factor equal to the depth divided by the depth plus the
surface elevation. Note that this scale factor varies as a function of the location in the wave train.
Standard Stokes 5th Wave This is a 5th order wave theory, also discussed in the previously mentioned references.
Modified Stokes 5th Wave This is a modification of the standard Stokes 5th theory. The modification is the same as
applied to the Airy theory.
Stream Function Wave This is Deans Stream Function theory, also discussed in the previously mentioned references.
Modified Stream Function Wave This is Deans Stream Function theory, modified to directly consider current in the
wave solution.
Stream Function Order When the Stream Function theory is activated, the solution order must be defined. Typical
values for the stream function order range from 3 to 13, and must be an "odd" value (see API-RP2A figure).
Water Depth This entry defines the vertical distance (in units of length) from the still water level (the surface) to the sea
bed.
Wave Height This entry defines the height of the incident wave. The height is the vertical distance (in units of length)
from the wave crest to the wave trough.
Wave Period This entry defines the time span (in seconds) for two successive wave crests to pass a fixed point.
Wave Kinematic Factor Because the two dimensional wave theories do not account for spreading, a reduction factor is
often used for the horizontal particle velocity and acceleration. Wave kinematic measurements support values in the range
of 0.85 to 0.95. Refer to the applicable offshore codes before using this item.
Wave Direction Cosines These entries define the direction of wave travel. These fields are unitless, and follow the
standard software global axis convention.
Wave Phase Angle This entry defines the position of the wave relative to the starting node of the piping system. The
phase angle is a measure (in degrees) of position in the wave train, where 0 is the wave crest, 180 is the wave trough, and
6-34 Technical Discussions
360 is the following crest. Since the wave propagates over the piping structure, each point in the structure experiences all
possible wave phase angles. One analysis technique specifies the wave phase at the system origin, and then the phase at
each node point in the model is determined. From these exact phase locations, the water particle data is computed from the
wave theory.
Alternatively, a conservative engineering approach is to use the same phase angle (usually zero) for all points in the model.
This technique produces higher loads; however, the extra conservatism is warranted when given the unknowns in specifying
environmental data.
Seawater Data
Free Surface Elevation This entry defines the height of the free surface, from the global system origin. If the system
origin is at the free surface, this entry should be specified as zero. If the system origin is at the sea bottom, this entry is equal
to the water depth. By default, the first node in a CAESAR II model is at an elevation of zero. This elevation can be changed
using the [Alt-G] key sequence.
Kinematic Viscosity This entry is used to define the kinematic viscosity of water. This value is used to determine the
Reynolds number, which is subsequently used to determine they hydrodynamic coefficients C
d
, C
m
, and C
l
. Typical values
of kinematic viscosity for sea water are listed in the table below.
Temp Deg (F) v(ft
2
/sec) Temp (C) v(m
2
/sec)
60 1.26
e-5
15.556 1.17058
e-6
50 1.46
e-5
10.000 1.35639
e-6
40 1.55
e-5
4.444 1.44000
e-6
30 2.00
e-5
-1.111 1.85807
e-6
Fluid Weight Density - This entry defines the weight density of the fluid. For sea water, this value is approximately
.037037 pounds per cubic inch (.001025 kg/cm3, 1.0256SG).
Piping Element Data
Element Exposure In implementing hydrodynamic loading in a software program, one must be able to indicate that
elements are either exposed to the fluid or not exposed to the fluid. In CAESAR II, this is accomplished by a set of radio
buttons, which indicate that the particular element is exposed to hydrodynamic loads, wind loads, or not exposed. This
specification carries forward for all subsequent elements, until changed.
Hydrodynamic Coefficients Piping elements which are to be subjected to hydrodynamic loading must have a drag (C
d
),
an inertia (C
m
), and a lift (C
l
) coefficient defined. The specification of these items is optional. A user may specify these
values as constants to be applied to all subsequent exposed elements, regardless of depth or phase position in the wave.
Alternatively, these values may be left blank, which will cause CAESAR II to interpolate their values from the charts
previously discussed.
Marine Growth This entry defines the amount of marine growth on the piping elements. The value of this entry is used
to increase the diameter of the piping elements. The units for this field are the current diameter units. The diameter used in
the computation of the hydrodynamic forces is equal to the pipe diameter plus twice the marine growth entry.
References
1 Mechanics of Wave Forces On Offshore Structures, Turgut Sarpkaya and Michael Isaacson, Van Nostrand Reinhold
Co., 1982, ISBN 0-442-25402-4.
2 Handbook of Ocean and Underwater Engineering, Myers, Holm, and McAllister, McGraw-Hill Book Co., 1969, ISBN
07-044245 -2.
Chapter 6 Technical Discussions 6-35
3 Fifth Order Gravity Wave Theory, Lars Skjelbreia and James Hendrickson, National Engineering Science Co.,
Pasadena, California, 1960.
4 Planning and Design of Fixed Offshore Platforms, McClelland and Reifel, Van Nostrand Reinhold Co., 1986, ISBN 0-
442-25223-4.
5 Intercomparison of Near-Bottom Kinematics by Several Wave Theories and Field and Laboratory Data, R. G. Dean and
M. Perlin, Coastal Engineering, #9 (1986), p399-437.
6 A Finite Amplitude Wave on a Linear Shear Current, R. A. Dalrymple, Journal of Geophysical Research, Vol 79, No
30, 1974.
7 Application of Stream Function Wave Theory to Offshore Design Problems, R. G. Dean, OTC #1613, 1972.
8 Stream Function Representation of Nonlinear Ocean Waves, R. G. Dean, Journal of Geophysical Research, Vol 70, No
18, 1965.
9 American Petroleum Institute - Recommended Practice 2A (API-RP2A), American Petroleum Institute, July 1993.
10 Improved Algorithm for Stream Function Wave Theory, Min-Chih Huang, Journal of Waterway, Port, Coastal, and
Ocean Engineering, January 1989.
11 Stream Function Wave Theory with Profile Constraints, Min-Chih Huang, Journal of Waterway, Port, Coastal, and
Ocean Engineering, January/February 1993.
6-36 Technical Discussions
Evaluating Vessel Stresses
The ASME Section VIII, Division 2 code provides for a fairly elaborate procedure to analyze the local stresses in vessels
and nozzles. Only the elastic analysis approach will be discussed in this manual. The user should always refer to the
applicable code if any of the limits described in this section are approached, or if any unusual material, weld, or stress
situation exists, or there are non-linear concerns such as the material's operation in the creep range.
The first step in the procedure is to determine if the elastic approach is satisfactory. Section AD-160 contains the exact
method and basically states that if all of the following conditions are met, then fatigue analysis need not be done:
1 The expected design number of full-range pressure cycles does not exceed the number of allowed cycles corresponding
to an S
a
value of 3S
m
(4S
m
for non-integral attachments) on the material fatigue curve. The S
m
is the allowable stress
intensity for the material at the operating temperature.
2 The expected design range of pressure cycles other than startup or shutdown must be less than 1/3 (1/4 for non-integral
attachments) the design pressure times (S
a
/S
m
), where S
a
is the value obtained on the material fatigue curve for the
specified number of significant pressure fluctuations.
3 The vessel does not experience localized high stress due to heating.
4 The full range of stress intensities due to mechanical loads (including piping reactions) does not exceed S
a
from the
fatigue curve for the expected number of load fluctuations.
Once the user has decided that an elastic analysis will be satisfactory, either a simplified or a comprehensive approach may
be taken to the vessel stress evaluation. Both methods will be described in detail below, after a discussion of the Section
VIII Div. 2 Requirements.
ASME Section VIII Division 2 - Elastic Analysis of Nozzle
Ideally, in order to address the local allowable stress problem, the user should have the endurance curve for the material of
construction and complete design pressure / temperature loading information. If any of the elastic limits are approached, or
if there is anything out of the ordinary about the nozzle/vessel connection design, the code should be carefully consulted
before performing the local stress analysis. The material S
m
table and the endurance curve for carbon steels are given in this
section for illustration. Only values taken directly from the code should be used in design.
There are essentially three criteria that must be satisfied before the stresses in the vessel wall due to nozzle loads can be
considered within the allowables. These three criteria can be summarized as:
P
m
< kS
mh
P
m
+ P
l
+ P
b
< 1.5kS
mh
P
m
+ P
l
+ P
b
+ Q < 3S
mavg
Where P
m
, P
l
, P
b
, and Q are the general primary membrane stress, the local primary membrane stress, the local primary
bending stress, and the total secondary stresses (membrane plus bending), respectively; and K, S
mh
, and S
mavg
are the
occasional stress factor, the hot material allowable stress intensity, and the average material stress intensity (S
mh
+ S
mc
) / 2.
Due to the stress classification defined by Section VIII, Division 2 in the vicinity of nozzles, as given in the Table 4-120.1,
the bending stress terms caused by any external load moments or internal pressure in the vessel wall near a nozzle or other
opening, should be classified as Q, or the secondary stresses, regardless of whether they were caused by sustained or
expansion loads. This causes P
b
to disappear, and leads to a much more detailed classification:
P
m
General primary membrane stress (primarily due to internal pressure)
P
l
Local primary membrane stress, which may include
--Membrane stress due to internal pressure
--Local membrane stress due to applied sustained forces and moments
QSecondary stresses, which may include
Chapter 6 Technical Discussions 6-37
--Bending stress due to internal pressure
--Bending stress due to applied sustained forces and moments
--Membrane stress due to applied expansion forces
--Bending stress due to applied expansion forces and moments
--Membrane stress due to applied expansion moments
Each of the stress terms defined in the above classifications contains three parts: two stress components in normal directions
and one shear stress component. To combine these stresses, the following rules apply:
Compute the normal and shear components for each of the three stress types, i.e. P
m
, P
l
, and Q;
Compute the stress intensity due to the P
m
and compare it against kS
mh
;
Add the individual normal and shear stress components due to P
m
and P
l
; compute the resultant stress intensity and
compare its value against 1.5kS
mh
;
Add the individual normal and shear stress components due to P
m
, P
l
, and Q, compute the resultant stress intensity, and
compare its value to against 3S
mavg
.
If there is an occasional load as well as a sustained load, these types may be repeated using a k value of 1.2.
These criteria can be readily found from Figure 4-130.1 of Appendix 4 of ASME Section VIII, Division 2 and the
surrounding text. Note that the primary bending stress term, Pb, is not applicable to the shell stress evaluation, and therefore
disappears from the Section VIII, Division 2 requirements. Under the same analogy, the peak stress limit may also be
written as:
P
l
+ P
b
+ Q + F < S
a
The preceding equation need not be satisfied, provided the elastic limit criteria of AD-160 is met based on the statement
explicitly given in Section 5-100, which is cited below:
If the specified operation of the vessel meets all of the conditions of AD-160, no analysis for cyclic operation is required
and it may be assumed that the peak stress limit discussed in 4-135 has been satisfied by compliance with the applicable
requirements for materials, design, fabrication, testing and inspection of this division.
Procedure to Perform Elastic Analyses of Nozzles
The procedure for checking stresses in vessel shells using WRC 107 can be summarized as follows:
1 Check geometric limitation to see whether WRC 107 is applicable;
2 If yes, check to see whether or not the elastic approach as outlined in Section VIII, Division 2, AD-160 is satisfactory;
3 Compute the sustained, expansion and occasional loads in the vessel shell due to the applied nozzle loads. Consider the
local restraint configuration in order to determine whether or not the axial pressure thrust load (P * A
in
) should be added
to the sustained (and occasional loads). If desired by the user, this thrust load will be automatically calculated and added
to the applied loads.
4 Calculate pressure stresses, P
m
, on the vessel shell wall in both longitudinal and circumferential (hoop) directions for
both sustained and occasional cases. Notice that two different pressure terms are required in carrying out the pressure
stress calculations. P is the design pressure of the system (sustained), while P
var
is the DIFFERENCE between the peak
pressure and the design pressure of the system, which will be used to qualify the vessel membrane stress under the
occasional load case.
Note: The P
m
stresses will be calculated automatically if a pressure value is entered by the user.
5 Run WRC 107 to calculate the P
l
, and Q stresses as defined earlier. Note that the local stresses due to sustained,
expansion and occasional loads can now be compute simultaneously.
6 Various stress components can be obtained from combining the stress intensities computed from applying the sustained,
expansion and occasional loads, if applicable. These stress intensities can then be used to carry out the stress
6-38 Technical Discussions
summations and the results are used to determine acceptability of the local stresses in the vessel shell. Notice now
CAESAR II can provide the WRC 107 stress summation module in line with the stress calculation routines
Under the above procedure, the equations used in CAESAR II to qualify the various stress components can be summarized as
follows:
P
m
(SUS) < S
mh
P
m
(SUS + OCC) < 1.2S
mh
P
m
(SUS) + P
l
(SUS) < 1.5S
mh
P
m
(SUS + OCC) + P
l
(SUS + OCC) < 1.5(1.2)S
mh
P
m
(SUS + OCC) + P
l
(SUS + OCC) + Q(SUS + EXP + OCC) < 1.5(S
mc
+ S
mh
)
Description of Alternate Simplified ASME Sect. VIII Div. 2 Nozzle Analysis
The most difficult problem associated with the comprehensive ASME Sect. VIII, Div. 2 nozzle/vessel analysis involves the
pressure calculation. Hoop and longitudinal hand pressure calculations can not be considered dependable, and axial pressure
loading on the junction is often calculated incorrectly or omitted. A smaller, yet significant problem with the comprehensive
calculation is the time it takes to organize and manipulate the stress data.
For these reasons, an alternate simplified approach was developed. To eliminate the concern for pressure, both the pressure
term in the loading on the left side of the inequality and the pressure term in the allowable on the right side of the inequality
are cancelled.
The first check is P
m
(due to pressure) must be less than or equal to 1.0 S
mh
. Assuming that the area reinforcement around
the nozzle will satisfy the pressure requirements, let this first check equal the maximum value.
The second check is P
m
+ P
l
+ P
b
must be less than or equal to 1.5 S
mh
. Subtracting the stresses due to pressure (assumed
equal to S
mh
) reduces this check to: P
l
+ P
b
(due to external sustained forces without pressure) < 0.5 S
mh
.
Unfortunately, the third check on the P
m
+ P
l
+ Q terms is at the root of an application controversy. There are primarily three
schools of thought:
P
m
+P
l
+Q is an operating loading condition, and as such, includes the loads due to pressure and weight.
P
m
+P
l
+Q is the range of loads, i.e. the expansion loading condition, and as such, excludes the effects of sustained, or
primary loads. Primary sustained loads, such as weight and pressure, should be excluded.
P
m
+P
l
+Q is the range of loads and should exclude the primary load weight, but should include the varying pressure load
at least in those thermal load cases where the system goes from a startup (ambient temperature and pressure condition to
operating condition).
For the simplification, it is assumed that the P
m
component due to pressure should be included in both the left and right side
of the P
m
+P
l
+P
b
+Q < 3S
m
inequality, thus assuming that the area reinforcement requirements are exactly satisfied, i.e.
Again, letting P
m
= S
m
and subtracting this pressure term from the expansion allowable (P
m
+ P
l
+ Q < 3S
m
) provides a
simplified allowable limit.
The expansion (or operating, or both) loads from the CAESAR II restraint report should satisfy the computed stress
requirement:
P
l
+ P
b
+ Q (operating or expansion excluding pressure) < 2S
m
.
In summary
Ensure proper nozzle reinforcement for pressure and assume pressure stresses are at their maximum.
Chapter 6 Technical Discussions 6-39
Compare primary stresses (without pressure) to 1/2 S
mh
.
Compare stresses due to the sum of primary and secondary loads to 2S
m(avg)
; where S
m(avg)
is the average of the hot and
cold allowable stress intensities (S
mh
& S
mc
).
Simplified ASME Sect. VIII Div. 2 Elastic Nozzle Analysis
1 Perform a CAESAR II analysis of the piping loads on the vessel/nozzle junction. Use WRC 297 flexibilities to compute
loads more accurately, but less conservatively (or do two analysis, one with flexibilities and one without). From this
analysis the user should have sustained, operating, and expansion loads on the vessel/nozzle junction.
2 Find S
mh
and S
mc
from the Sect. VIII allowable stress tables. S
mh
is the vessel material hot allowable, and S
mc
is the
vessel material cold allowable.
3 Run WRC 107 with the sustained loads on the vessel/nozzle junction from CAESAR II, and make sure that the computed
stress intensities are less than 0.5 S
mh
. This conservatively considers bending stresses from internal pressure and
sustained moments to have a primary classification; if it fails, the stresses must be reviewed in more detail.
4 Run WRC 107 with the operating loads on the vessel/nozzle junction from CAESAR II, and make sure that the computed
stress intensities are less than S
mh
+ S
mc
.
5 Run WRC 107 with the expansion loads on the vessel/nozzle junction from CAESAR II, and make sure that the
computed stress intensities are less than S
mh
+ S
mc
.
Should any of the checks described fail, then the more comprehensive analysis (described earlier) of the junction should be
performed.
6-40 Technical Discussions
Inclusion of Missing Mass Correction
The response of a system under a dynamic load is often determined by superposition of modal results, with CAESAR II
specifically providing the spectral analysis method for use. One of the advantages of modal analysis is that usually only a
limited number of modes are excited and need be included in the analysis. The drawback to this method is that although
displacements may be obtained with good accuracy using only a few of the lowest frequency modes, the force, reaction, and
stress results may require extraction of far more modes (possibly far into the rigid range) before acceptable accuracy is
attained. CAESAR IIs Missing Mass option offers the ability to include a correction which represents the quasi-static
contribution of the higher order modes not explicitly extracted for the modal/dynamic response, thus providing greater
accuracy with reduced calculation time.
The dynamic response of a linear multi-degree-of-freedom system is described by the following equation:
Ma(t) + Cv(t) + Kx(t) = F(t)
Where:
M = n x n mass matrix of system
C = n x n damping matrix of system
K = n x n stiffness matrix of system
a(t) = n x 1, time-dependent acceleration vector
v(t) = n x 1, time-dependent velocity vector
x(t) = n x 1, time-dependent displacement vector
F(t) = n x 1, time-dependent applied force vector
Assuming harmonic motion and neglecting damping, the free vibration eigenvalue problem for this system is
Ku - Mu e
2
= 0
Where:
u = n x n mode shape matrix
e
2
= n x n matrix where each diagonal entry is the frequency squared of the corresponding mode
The modal matrix u may be normalized such that u
T
M u = I (where I is the n x n identity matrix) and u
T
K u = e
2
.
The modal matrix u may be partitioned into two submatrices:
u = [ u
e
u
r
]
Where:
u
e
= mode shapes extracted for dynamic analysis (i.e., lowest frequency modes)
u
r
= residual (non-extracted) mode shapes (corresponding to rigid response, or the missing mass
contribution)
The extracted mode shapes are orthogonal to the residual mode shapes, or:
u
e
T
x u
r
= 0
Chapter 6 Technical Discussions 6-41
The displacement components can be expressed as linear combinations of the mode shapes:
x = uY = u
e
Y
e
+ u
r
Y
r
= x
e
+ x
r
Where:
x = total system displacements
x
e
= system displacements due to extracted modes
x
r
= system displacements due to residual modes
Y = generalized modal coordinates
Y
e
= partition of Y matrix corresponding to extracted modes
Y
r
= partition of Y matrix corresponding to residual modes
The dynamic load vector can be expressed in similar terms:
F = K u Y = K u
e
Y
e
+ K u
r
Y
r
= F
e
+ F
r
Where:
F = total system load vector
F
e
= load vector due to extracted modes
F
r
= load vector due to residual modes
Y = generalized modal coordinates
Y
e
= partition of Y matrix corresponding to extracted modes
Y
r
= partition of Y matrix corresponding to residual modes
Normally, modal superposition analyses completely neglect the rigid response the displacements X
r
caused by the load
F
r
. This response, of the non-extracted modes, can be obtained from the system displacement under a static loading F
r
.
Based upon the relationships stated above, F
r
can be estimated as follows:
F = K u
e
Y
e
+ K u
r
Y
r
Multiplying both sides by u
e
T
(and considering that u
e
T
u
r
= 0):
u
e
T
F = u
e
T
K u
e
Y
e
+ u
e
T
K u
r
Y
r
= u
e
T
K u
e
Y
e
Substituting e
e
2
for u
e
T
K u
e
and solving for Y
e
:
u
e
T
F = e
e
2
Y
e
Y
e
= u
e
T
e
e
-2
F
The residual force can now be stated as
F
r
= F - K u
e
Y
e
= F - u
e
T
K u
e
e
e
-2
F
As seen earlier
u
T
M u e
2
= I e
2
= u
T
K u
Substituting u
e
T
Mu
e
e
e
2
for u
e
T
K u
e
:
F
r
= F - u
e
T
M u
e
e
e
2
e
e
-2
F = F - u
e
T
M u
e
F
6-42 Technical Discussions
Therefore, CAESAR II calculates the residual response (and includes it as the missing mass contribution) according to the
following procedure:
1 The missing mass load is calculated for each individual shock load as
F
r
= F - u
e
T
M u
e
F
Note: The load vector F represents the product of the force set vector and the rigid DLF for force spectrum loading; the
product of the mass matrix, ZPA, and directional vector for non-ISM seismic loads; and the product of the mass matrix,
ZPA, and displacement matrix (under unit ISM support displacement) for seismic anchor movement loads. Note that the
missing mass load will vary, depending upon the number of modes extracted by the user and the cutoff frequency selected
(or more specifically, the DLF or acceleration corresponding to the cutoff frequency). "Rigid, for the purposes of
determining the rigid DLF, or the ZPA, may be designated by the user, through a setup parameter, to be either the
DLF/acceleration associated with the frequency of the last extracted mode, or the true spectral DLF/ ZPAthat
corresponding to the largest entered frequency of the input spectrum.
2 The missing mass load is applied to the structure as a static load. The static structural response is then combined
(according to the user-specified combination method) with the dynamically amplified modal responses as if it were a
modal response. Actually this static response is the algebraic sum of the responses of all non-extracted modes
representing in-phase response, as would be expected from rigid modes.
3 The Missing Mass Data report is compiled for all shock cases, whether missing mass is to be included or not. The
percent of mass active is calculated according to:
% Active Mass = 1 - ( F
r
[i] / F [i])
summed over i = 1 to n
The maximum possible percent that is theoretically possible for this value is of course 100%, however numerical
inaccuracies may occasionally cause the value to be slightly higher. If the missing mass correction factor is included, the
percent of mass included in the correction is shown in the report as well.
Chapter 6 Technical Discussions 6-43
Since CAESAR IIs procedure assumes that the missing mass correction represents the contribution of rigid modes, and that
the ZPA is based upon the spectral ordinate value at the frequency of the last extracted mode, it is recommended that the
user extract modes up to, but not far beyond, a recognized rigid frequency. Choosing a cutoff frequency to the left of the
spectrums resonant peak will provide a non-conservative result, since resonant responses may be missed. Using a cutoff
frequency to the right of the peak, but still in the resonant range, will yield conservative results, since the ZPA/rigid DLF
will be overestimated. Extracting a large number of rigid modes for calculation of the dynamic response may be
conservative, since all available modal combination methods (SRSS, GROUP, ABS, etc.) give conservative results versus
the algebraic combination method which gives a more realistic representation of the net response of the rigid modes. Based
upon the response spectrum shown below, an appropriate cutoff point for the modal extraction would be about 33 Hz.
Maximum Stress vs. Extracted Nodes
CAESAR II provides two options for combining the missing mass correction with the modal (dynamic) resultsSRSS and
Absolute. The Absolute combination method of course provides the more conservative result, and is based upon the
assumption that the dynamic amplification is going to occur simultaneously with the maximum ground acceleration or force
load. Literature (References 1, 2) states that the modal and the rigid portions of the response to typical dynamic loads are
actually statistically independent, so that an SRSS Combination method is a more accurate representation of reality. For this
reason, CAESAR IIs default missing mass combination method is SRSS.
References
1 A. K. Gupta, Response Spectrum Method in Seismic Analysis and Design of Structures, CRC Press, 1990
2 K. M. Vashi, Computation of Seismic Response from Higher Frequency Modes, ASME 80-C2/PVP-50, 1980
3 O. E. Hansteen and K. Bell, On the Accuracy of Mode Superposition Analysis in Structural Dynamics, Earthquake
Engineering and Structural Dynamics, Volume 7, John Wiley & Sons, Ltd., 1979
6-44 Technical Discussions
Fatigue Analysis Using CAESAR II
For most piping codes supported by CAESAR II, performance of fatigue analysis is an extension to, rather than an explicit
part of, the code requirements (however, it is an explicit part of the IGE/TD/12 Pipework Stress Analysis for Gas Industry
Plant code).
Fatigue Basics
Piping and vessels have been known to suffer from sudden failure following years of successful service. Research done
during the 1940s and 1950s (primarily advanced by A. R. C. Markls Piping Flexibility Analysis, published in 1955)
provided an explanation for this phenomenon, as well as design criteria aimed at avoiding failures of this type. The
explanation was that materials were failing due to fatigue, a process leading to the propagation of cracks, and subsequent
fracture, following repeated cyclic loading.
Steels and other metals are made up of organized patterns of molecules, known as crystal structures. However, these
patterns are not maintained throughout the steel producing an ideal homogeneous material, but are found in microscopic
isolated island-like areas called grains. Inside each grain the pattern of molecules is preserved. From one grain boundary to
the next the molecular pattern is the same, but the orientation differs. As a result, grain boundaries are high energy borders.
Plastic deformation begins within a grain that is both subject to a high stress and oriented such that the stress causes a
slippage between adjacent layers in the same pattern. The incremental slippages (called dislocations) cause local cold-
working. On the first application of the stress, dislocations will move through many of the grains that are in the local area of
high stress. As the stress is repeated, more dislocations will move through their respective grains. Dislocation movement is
impeded by the grain boundaries, so after multiple stress applications, the dislocations tend to accumulate at grain
boundaries, eventually becoming so dense that the grains lock up, causing a loss of ductility and thus preventing further
dislocation movement. Subsequent applications of the stress cause the grain to tear, forming cracks. Repeated stress
applications cause the cracks to grow. Unless abated, the cracks propagate with additional stress applications until sufficient
cross sectional strength is lost to cause catastrophic failure of the material.
The fatigue capacity of a material can be estimated through the application of cyclic tensile/compressive displacement loads
with a uniaxial test machine. A plot of the cyclic stress capacity of a material is called a fatigue (or endurance) curve. These
curves are generated through multiple cyclic tests at different stress levels. The number of cycles to failure usually increases
as the applied cyclic stress decreases, often until a threshold stress (known as the endurance limit) is reached below which
no fatigue failure occurs, regardless of the number of applied cycles. An endurance curve for carbon and low alloy steels,
taken from the ASME Section VIII Division 2 Pressure Vessel Code is shown in the following figure.
Chapter 6 Technical Discussions 6-45
Fatigue Analysis of Piping Systems
IGE/TD/12 does, on the other hand, present specific requirements for true fatigue evaluation of systems subject to a cyclic
loading threshold. Furthermore, ASME Section III, Subsection NB and ASME Section VIII Division 2 provide guidelines
by which fatigue evaluation rules may be applied to piping (and other pressure retaining equipment). These procedures have
been adapted, where possible, to CAESAR IIs methodology.
Performing Fatigue Analyses:
1 Assigning fatigue curve data to the piping material: This is done on the Allowable auxiliary screen. Fatigue data may
be entered directly, or read in from a text file (a number of commonly used curves have been provided). Users may
define their own fatigue curves as defined later in this section.
2 Defining the fatigue load cases: This may be done in either the static or dynamic load case builders. For this purpose, a
new stress type, FAT, has been defined. For every fatigue case, the number of anticipated cycles must also be defined.
3 Calculation of the fatigue stresses: This is done automatically by CAESAR II the fatigue stresses, unless explicitly
defined by the applicable code are calculated the same as CAESAR II calculates stress intensity, in order to conform to
the requirements of ASME Section VIII, Division 2 Appendix 5. (The IGE/TD/12 is currently the only piping code
supported by CAESAR II which does have explicit instructions for calculating fatigue stresses.) The equations used in the
calculation of fatigue stresses are documented at the end of this section.
4 Determination of the allowable fatigue stresses: Allowables are interpolated logarithmically from the fatigue curve
based upon the number of cycles designated for the load case. For static load cases, the calculated stress is assumed to
be a peak-to-peak cyclic value (i.e., thermal expansion, settlement, pressure, etc.), so the allowable stress is extracted
6-46 Technical Discussions
directly from the fatigue curve. For harmonic and dynamic load cases, the calculated stress is assumed to be a zero-to-
peak cyclic value (i.e., vibration, earthquake, etc.), so the extracted allowable is divided by 2 prior to use in the
comparison.
5 Determination of the allowable number of cycles: The flip side of calculating the allowable fatigue stress for the
designated number of cycles is the calculation of the allowable number of cycles for the calculated stress level. This is
done by logarithmically interpolating the Cycles axis of the fatigue curve based upon the calculated stress value.
Since static stresses are assumed to be peak-to-peak cyclic values, the allowable number of cycles is interpolated
directly from the fatigue curve. Since harmonic and dynamic stresses are assumed to be zero-to-peak cyclic values, the
allowable number of cycles is interpolated using twice the calculated stress value.
6 Reporting the results: CAESAR II provides two reports for viewing the results of load cases of stress type FAT. The first
of these is the standard stress report, which displays the calculated fatigue stress and fatigue allowable at each node.
Stress reports may be generated individually for each load case, and show whether any of the individual load cases in
isolation would fail the system.
However, in those circumstances where there is more than one cyclic load case potentially contributing to fatigue failure,
the Cumulative Usage report is appropriate. In order to generate this report, the user selects all of the FAT load cases which
contribute to the overall system degradation. The Cumulative Usage report lists for each node point the usage ratio (actual
cycles divided by allowable cycles), and then sums these up for total Cumulative Usage. A total greater than 1.0 indicates a
potential fatigue failure.
Static Analysis Fatigue Example
Consider a sample job that potentially has several different cyclic load variations:
1 Operating cycle from ambient (70F) to 500F (12,000 cycles anticipated)
2 Shut down external temperature variation from ambient (70F) to -20F (200 cycles anticipated)
3 Pressurization to 1800 psig (12,000 cycles anticipated)
4 Pressure fluctuations of plus/minus 30 psi from the 1800 psig (200,000 cycles anticipated)
In order to do a proper fatigue analysis, these should be grouped in sets of load pairs which represent the worst-case
combination of stress ranges between extreme states. These load variations can be laid out in graphical form. The figure
below shows a sketch of the various operating ranges this system experiences. Each horizontal line represents an operating
range. At the each end of each horizontal line, the temperatures and pressures defining the range are noted. At the center of
each horizontal line, the number of cycles for each range is defined.
Using this sketch of the operating ranges, the four fatigue load cases can be determined. The procedure is as follows.
Chapter 6 Technical Discussions 6-47
Case 1: Cover the absolute extreme, from 20F and 0 psi to 500F and 1830 psi. This occurs 200 times. As a result of this
case, the cycles for the ranges defined must be reduced by 200. The first range (-20,0 to 70,0) is reduced to zero, and has no
contribution to additional load cases. The second range (70,0 to 500,1800) is reduced to 11,800 cycles. The third and fourth
ranges are similarly reduced to 199,800 cycles.
These same steps can be used to arrive at cases 2 through 4, reducing the number of considered cycles at each step. This
procedure is summarized in the table below.
Segment -20, 0 to 70, 0 70, 0 to 500, 1800 500, 1700 to 500, 1800 500, 1800 to 500, 1830
Case
Initial 200 12,000 200, 000 200,000
After 1 0 11,800 200, 000 199,800
After 2 0 0 200, 000 188,000
After 3 0 0 12,000 0
After 4 0 0 0 0
This table is then used to set the load cases as cycles between the following load values:
Between -20F, 0 psig and 500F, 1830 psig (200 cycles)
Between 70F, 0 psig and 500F, 1830 psig (11,800 cycles)
Between 500F, 1770 psig and 500F, 1830 psig (188,000 cycles)
Between 500F, 1770 psig and 500F, 1800 psig (12,000 cycles)
6-48 Technical Discussions
These temperatures and pressures are entered as operating conditions accordingly:
Static Analysis Fatigue Example
It is next necessary to enter the fatigue curve data for the material. This is done by clicking the Fatigue Curves button,
revealing the Material Fatigue Curve dialog box. This can be used to enter the fatigue curve for the material (note: for
IGE/ TD/12 code it is necessary to enter five sets of fatigue curves, for fatigue classes D, E, F, G, and W). Up to eight Cycle
vs. Stress data points may be entered to define the curve; interpolations are made logarithmically. Cycle/Stress pairs should
be entered in ascending order (ascending by cycles). Stress values should be entered as allowable Stress Range, rather than
allowable Stress Amplitude.
Chapter 6 Technical Discussions 6-49
Material Fatigue Curves Dialog
Fatigue curves may be alternatively acquired from a text file, by clicking on the Read from file button. This displays a
list of all \CAESAR\SYSTEM\*.FAT files.
Read from File Dialog
Shipped with the program are the following fatigue curve files (the user may easily construct additional fatigue curve files,
as described in Appendix A below):
5-110-1A.FAT ASME Section VIII Division 2 Figure 5-110.1, UTS < 80 ksi
5-110-1B.FAT ASME Section VIII Division 2 Figure 5-110.1, UTS = 115-130 ksi
5-110-2A.FAT ASME Section VIII Division 2 Figure 5-110.2, Curve A
5-110-2B.FAT ASME Section VIII Division 2 Figure 5-110.2, Curve B
5-110-2C.FAT ASME Section VIII Division 2 Figure 5-110.2, Curve C
6-50 Technical Discussions
In this case, for A106B low carbon steel, operating at 500F, 5-110-1A.FAT is the appropriate selection. This populates the
fatigue curve data:
A106B Low Carbon Steel Example Fatigue Curve Data
At this point, users can error check the job, and the load cases can be set up.
The static load case builder offers a new stress type, FAT (fatigue). Selecting this stress type does the following:
1 Invites the user to define the number of cycles for the load case (dragging the FAT stress type into the load case or
pressing the Load Cycles button opens the Load Cycles field),
2 Causes the stress range to be calculated as per the fatigue stress method of the governing code (currently this is stress
intensity for all codes except IGE/TD/12).
3 Causes the calculated stress range to be compared to the full value extracted from the fatigue curve, and
4 Indicates that the load case may be included in the Cumulative Usage report.
The last four load cases represent the load set pairs defined earlier.
Chapter 6 Technical Discussions 6-51
Example with Fatigue Load Cases Defined in the Load Case Editor
Once the job has been run, note that the presence of a FAT stress type adds the Cumulative Usage report to the list of
available reports.
6-52 Technical Discussions
Static Output Processor
The fatigue stress range may be checked against the fatigue curve allowable for each load case by simply selecting it along
with the Stresses report. Review of each load case shows that all stress levels pass.
Chapter 6 Technical Discussions 6-53
Fatigue Stress Report
6-54 Technical Discussions
However, this is not a true evaluation of the situation, because it is not a case of either-or. The piping system is subjected
to all of these load cases throughout its expected design life, not just one of them. Therefore, we must review the
Cumulative Usage report, which shows the total effect of all fatigue load cases (or any combination selected by the user)
on the design life of the system. This report lists for each load case the expected number of cycles, the allowable number of
cycles (based upon the calculated stress), and the Usage Ratio (actual cycles divided by allowable cycles). The Usage Ratios
are then summed for all selected load cases; if this sum exceeds 1.0, the system has exceeded its fatigue capabilities. In this
case, it is apparent that the sum of all of the cyclic loadings at node 115 can be expected to fail this system:
Cumulative Usage Report
Chapter 6 Technical Discussions 6-55
Fatigue Capabilities in Dynamic Analysis
Fatigue analysis capability is also available for harmonic and dynamic analyses as well. Harmonic load cases are entered as
they always have been; they may be designated as being stress type FAT simply by entering the number of expected load
cycles on the harmonic input screen:
Harmonic Input Screen
This produces the same types of reports as are available for the static analysis; they can be processed as discussed earlier.
6-56 Technical Discussions
Static Output Processor
The only difference between the harmonic and static fatigue analyses is that for harmonic jobs, the calculated stresses are
assumed to be zero-to-peak calculations, so they are compared to only half of the stress value extracted from the fatigue
curve. Likewise, when creating the Cumulative Usage report, the number of allowable cycles is based upon twice the
calculated stress.
For other dynamic applications (response spectrum and time history), the stress type may be identified as fatigue by
selecting the stress type from the drop list for the Load Case or Static/Dynamic Combination, and by entering the number of
expected cycles in the provided field.
Note that as with the harmonic analyses, the calculated stresses are assumed to be zero-to-peak calculations, so they are
compared to only half of the stress value extracted from the fatigue curve. Likewise, when creating the Cumulative Usage
report, the number of allowable cycles is based upon twice the calculated stress.
Chapter 6 Technical Discussions 6-57
Creating the .FAT Files
The .FAT file is a simple text file, containing the data points necessary to describe the fatigue curve for the material, for
both butt welded and fillet welded fittings. A sample FAT file is shown below.
* ASME SECTION VIII DIVISION 2 FATIGUE CURVE
* FIGURE 5-110.1
* DESIGN FATIGUE CURVES FOR CARBON, LOW ALLOY, SERIES 4XX,
* HIGH ALLOY AND HIGH TENSILE STEELS FOR TEMPERATURES NOT
* EXCEEDING 700 F
* FOR UTS s 80 KSI
*
0.5000000 - STRESS MULTIPLIER (PSI); ALSO CONVERTS AMPLITUDE TO FULL RANGE
*
10 580000.0
100 205000.0
1000 83000.0
10000 38000.0
100000 20000.0
500000 13500.0
1000000 12500.0
0 0.0
*
This text file can be created using any available text editor. Any line beginning with an asterisk is treated as a comment
line. It is highly recommended that comment lines be used so that the data can be related back to a specific material curve.
The first actual data line in the file is a stress multiplier. This value is used to adjust the data values from zero to peak to
peak to peak and/or to convert the stress levels to psi (the entered values will be divided by this number -- i.e., if the stress
values in the file represent a stress amplitude, in psi, rather than a range, this "stress multiplier should be 0.5). Following
this line is the fatigue curve data table. This table consists of eight lines, of two columns. The first column is the Cycle
column, the second column is the Stress column. For each value in the cycle column, the corresponding stress value from
the material fatigue curve should be listed in the stress column.
Fatigue curves intended for use in the IGE/TD/12 code are built slightly different. The first data line contains not one, but
three values: the stress multiplier described above, a modulus of elasticity correction, and a modulus of elasticity
multiplier (the correction factor is divided by this to convert to psi) upon file read, the modulus of elasticity correction
is inserted into the appropriate field on the fatigue curve screen. Furthermore, the IGE/TD/12 fatigue files include five
fatigue curves (sequentially Fatigue Class D, E, F, G, and W), rather than one. Optional comment lines may be used to
separate the tables these comments aid in the readability of the data file. The format of the IGE/TD/12 fatigue files can
best be determined by reviewing the contents of the file TD12ST.FAT.
In all tables, the number of cycles increases as you work down the table. If there is not enough data to utilize all eight lines,
unused lines should be populated with zeroes.
6-58 Technical Discussions
Calculation of Fatigue Stresses
For IGE/TD/12 the computation of fatigue stresses is detailed in Section 5.4.4 of that code. This section of the code states:
"The principal stress in any plane can be calculated for any set of conditions from the following formula:"
Where,
S
h
= Hoop stress
S
a
= Axial stress
S
q
= Shear stress
"This should be used for establishing the range of stress, due regard being paid to the direction and sign." For all other
piping codes in CAESAR II, the fatigue stress is computed as the stress intensity, as follows:
3D Maximum Shear Stress Intensity (Default)
SI = Maximum of:
S1OT - S3OT
S1OB - S3OB
Max(S1IT,RPS) - Min(S3IT,RPS)
Max(S1IB,RPS) - Min(S3IB,RPS)
Where:
S1OT=Maximum Principal Stress, Outside Top
= (SLOT+HPSO)/2.0+(((SLOT-HPSO)/2.0)
2
+TSO
2
)1/2
S3OT=Minimum Principal Stress, Outside Top
=(SLOT+HPSO)/2.0-(((SLOT-HPSO)/2.0)2+TSO2) 1/2
S1IT=Maximum Principal Stress, Inside Top
=(SLIT+HPSI)/2.0+(((SLIT-HPSI)/2.0)
2
+TSI
2
) 1/2
S3IT=Minimum Principal Stress, Inside Top
=(SLIT+HPSI)/2.0-(((SLIT-HPSI)/2.0)
2
+TSI
2
) 1/2
S1OB=Maximum Principal Stress, Outside Top
=(SLOB+HPSO)/2.0+ (((SLOB-HPSO)/2.0)
2
+TSO
2
) 1/2
S3OB=Minimum Principal Stress, Outside Bottom
=(SLOB+HPSO)/2.0- (((SLOB-HPSO)/2.0)
2
+TSO
2
) 1/2
Chapter 6 Technical Discussions 6-59
S1IB=Maximum Principal Stress, Inside Bottom
=(SLIB+HPSI)/2.0+ (((SLIB-HPSI)/2.0)
2
+TSI
2
) 1/2
S3IB=Minimum Principal Stress, Inside Bottom
=(SLIB+HPSI)/2.0- (((SLIB-HPSI)/2.0)
2
+TSI
2
) 1/2
RPS=Radial Pressure Stress, Inside
HPSI=Hoop Pressure Stress (Inside, from Lame's Equation)
HPSO=Hoop Pressure Stress (Outside, from Lame's Equation)
SLOT=Longitudinal Stress, Outside Top
SLIT=Longitudinal Stress, Inside Top
SLOB=Longitudinal Stress, Outside Bottom
SLIB=Longitudinal Stress, Inside Bottom
TSI=Torsional Stress, Inside
TSO=Torsional Stress, Outside
6-60 Technical Discussions
Pipe Stress Analysis of FRP Piping
Underlying Theory
The behavior of steel and other homogeneous materials has been long understood, permitting their widespread use as
construction materials. The development of the piping and pressure vessel codes (Reference 1) in the early part of this
century led to the confidence in their use in piping applications; the work of Markl et. al. in the 1940s and 1950s was
responsible for the formalization of todays pipe stress methods, leading to an ensuing diversification of piping codes on an
industry by industry basis. The advent of the digital computer, and with it the appearance of the first pipe stress analysis
software (Reference 2), further increased the confidence with which steel pipe could be used in critical applications. The
1980s saw the wide spread proliferation of the micro computer, with associated pipe stress analysis software, which in
conjunction with training, technical support, and available literature, has brought stress analysis capability to almost all
engineers. In short, an accumulated experience of close to 100 years, in conjunction with ever improving technology has led
to the utmost confidence on the part of todays engineers when specifying, designing, and analyzing steel, or other metallic,
pipe.
For fiberglass reinforced plastic (FRP) and other composite piping materials, the situation is not the same. Fiberglass
reinforced plastic was developed only as recently as the 1950s, and did not come into wide spread use until a decade later
(Reference 3). There is not a large base of stress analysis experience, although not from a lack of commitment on the part of
FRP vendors. Most vendors conduct extensive stress testing on their components, including hydrostatic and cyclic pressure,
uniaxial tensile and compressive, bending, and combined loading tests. The problem is due to the traditional difficulty
associated with, and lack of understanding of, stress analysis of heterogeneous materials. First, the behavior and failure
modes of these materials are highly complex and not fully understood, leading to inexact analytical methods, and a general
lack of agreement on the best course of action to follow. This lack of agreement has slowed the simplification and
standardization of the analytical methods into universally recognized codes (BS 7159 Code (Design and Construction of
Glass Reinforced Plastics Piping Systems for Individual Plants or Sites) and UKOOA Specification and
Recommended Practice for the Use of GRP Piping Offshore being notable exceptions). Secondly, the heterogeneous,
orthotropic behavior of FRP and other composite materials has hindered the use of the pipe stress analysis algorithms
developed for homogeneous, isotropic materials associated with crystalline structures. A lack of generally accepted
analytical procedures has contributed to a general reluctance to use FRP piping for critical applications.
Stress analysis of FRP components must be viewed on many levels. These levels, or scales, have been called Micro-Mini-
Macro levels, with analysis proceeding along the levels according to the MMM principle (Reference 4).
Micro-Level Analysis
Stress analysis on the Micro level refers to the detailed evaluation of the individual materials and boundary mechanisms
comprising the composite material. In general, FRP pipe is manufactured from laminates, which are constructed from
elongated fibers of a commercial grade of glass (called E-glass), which are coated with a coupling agent or sizing prior to
being embedded in a thermosetting plastic material, typically epoxy or polyester resin.
This means, on the micro scale, that an analytical model must be created which simulates the interface between these
elements. Since the number and orientation of fibers is unknown at any given location in the FRP sample, the simplest
representation of the micro-model is that of a single fiber, extending the length of the sample, embedded in a square profile
of matrix.
Evaluation of this model requires use of the material parameters of
1 the glass fiber
2 the coupling agent or sizing layer (normally of such microscopic proportion that it may be ignored)
3 the plastic matrix
It must be considered that these material parameters may vary for an individual material based upon tensile, compressive, or
shear applications of the imposed stresses, and typical values vary significantly between the fiber and matrix (Reference 5):
Chapter 6 Technical Discussions 6-61
Young's
Modulus
Ultimate
Strength
Coefficient of
Thermal Expansion
Material tensile (MPa) tensile (MPa) m/m/C
7.25 x 10
3
1.5 x 10
3
5.0 x 10
-6
2.75 x 10
3
7.0x 10
3
7.0 x 10
-3
The following failure modes of the composite must be similarly evaluated:
failure of the fiber
failure of the coupling agent layer
failure of the matrix
failure of the fiber-coupling agent bond
failure of the coupling agent-matrix bond
Because of uncertainties about the degree to which the fiber has been coated with the coupling agent and about the nature of
some of these failure modes, this evaluation is typically reduced to
failure of the fiber
failure of the matrix
failure of the fiber-matrix interface
Micro-Level GRP Sample-- Single Fiber Embedded in Square Profile of Matrix
Stresses in the individual components can be evaluated through finite element analysis of the strain continuity and
equilibrium equations, based upon the assumption that there is a good bond between the fiber and matrix, resulting in
compatible strains between the two. For normal stresses applied parallel to the glass fiber:
c
f
= c
m
= o
af
/ E
f
= o
am
/ E
m
o
af
= o
am
E
f
/ E
m
Where:
c
f
= strain in the fiber
c = strain in the matrix
o
af
= normal stress parallel to fiber, in the fiber
E
f
= modulus of elasticity of the fiber
o
am
= axial normal stress parallel to fiber, in the matrix
E = modulus of elasticity of the matrix
6-62 Technical Discussions
Due to the large ratio of the modulus of elasticity of the fiber to that of the matrix, it is apparent that nearly all of the axial
normal stress in the fiber-matrix composite is carried by the fiber. Exact values are (Reference 6):
o
af
= o
L
/ [| + (1-|)E
m
/E
f
]
o
am
= o
L
/ [|E
m
/E
f
+ (1-|)]
Where:
o
L
= nominal longitudinal stress across composite
| = glass content by volume
The continuity equations for the glass-matrix composite seem less complex for normal stresses perpendicular to the fibers,
since the weak point of the material seems to be limited by the glass-free cross-section shown in the following figure.
For this reason, it would appear that the strength of the composite would be equal to that of the matrix for stresses in this
direction; in fact, its strength is less than that of the matrix due to stress intensification in the matrix caused by the irregular
stress distribution in the vicinity of the stiffer glass. (Since the elongation over distance D
1
must be equal to that over the
longer distance D
2
, the strain, and thus the stress at location D
1
must exceed that at D
2
by the ratio
D
2
/D
1
.) Maximum
intensified transverse normal stresses in the composite are:
( )
1.25
2
2 2
1 ( ) /(1 )
(1 0.85 )[1 (2 3 )1 ( )(1 )]
m f m
m f m
E E V
E E V
|
(
o | + |
(
o =
+ | | t
Where:
o
b
= intensified normal stress transfer to the fiber in the composite
o
a
= nominal transverse normal stress across composite
V = Poissons ratio of the matrix
Note: Because of the Poisson effect, this stress produces an additional s'
am
equal to the following:
o
am
= V
m
o |
Shear stress can be allocated to the individual components again through the use of continuity equations; it would appear
that the stiffer glass would resist the bulk of the shear stresses; however, unless the fibers are infinitely long, all shears must
Chapter 6 Technical Discussions 6-63
eventually pass through the matrix in order to get from fiber to fiber. Shear stress between fiber and matrix can be estimated
as
1.25
m f
o
2
m f
T(1-p) +p(G /G )
q =
(1+0.6rp )1-r( 2rp3 l)1-(G /G )
Where:
t
ab
= intensified shear stress in composite
T = nominal shear stress across composite
G
m
= shear modulus of elasticity in matrix
G
f
= shear modulus of elasticity in fiber
Determination of the stresses in the fiber-matrix interface is more complex. The bonding agent has an inappreciable
thickness, and thus has an indeterminate stiffness for consideration in the continuity equations. Also, the interface behaves
significantly differently in shear, tension, and compression, showing virtually no effects from the latter. The state of the
stress in the interface is best solved by omitting its contribution from the continuity equations, and simply considering that it
carries all stresses which must be transferred from fiber to matrix.
Once the stresses have been apportioned, they must be evaluated against appropriate failure criteria. The behavior of
homogeneous, isotropic materials such as glass and plastic resin, under a state of multiple stress is better understood. A
failure criterion for isotropic material reduces the combined normal and shear stresses (s
a
, s
b
, s
c
, t
ab
, t
ac
, t
bc
) to a single stress,
an equivalent stress, which can be compared to the tensile stress present at failure in a material under uniaxial loading, i.e.
the ultimate tensile stress, S
ult
.
Different theories, and different equivalent stress functions f(s
a
, s
b
, s
c
, t
ab
,
tac
, t
bc
) have been proposed, with possibly the most
widely accepted being the Huber-von Mises-Hencky criterion, which states that failure will occur when the equivalent stress
reaches a critical value the ultimate strength of the material:
o
eq
= \{1/2 [(o
a
- o
b
)
2
+ (o
a
- o
c
)
2
+ (o
b
- o
c
)
2
] + 6(t
ab
2
+ t
ac
2
+ t
bc
2
)} s S
ult
This theory does not fully cover all failure modes of the fiber, in that it omits reference to direction of stress (i.e., tensile vs.
Compressive). The fibers, being relatively long and thin, predominantly demonstrate buckling as their failure mode when
loaded in compression.
6-64 Technical Discussions
The equivalent stress failure criterion has been corroborated (with slightly non-conservative results) by testing. Little is
known about the failure mode of the adhesive interface, although empirical evidence points to a failure criterion which is
more of a linear relationship between the normal and the square of the shear stresses. Failure testing of a composite material
loaded only in transverse normal and shear stresses are shown in the following figure; the kink in the curve shows the
transition from the matrix to the interface as the failure point.
Mini-Level Analysis
Although feasible in concept, micro level analysis is not feasible in practice. This is due to the uncertainty of the
arrangement of the glass in the compositethe thousands of fibers which may be randomly distributed, semi-randomly
oriented (although primarily in a parallel pattern), and of randomly varying lengths. This condition indicates that a sample
can truly be evaluated only on a statistical basis, thus rendering detailed finite element analysis inappropriate.
For mini-level analysis, a laminate layer is considered to act as a continuous (hence the common reference to this method as
the continuum method) material, with material properties and failure modes estimated by integrating them over the
assumed cross-sectional distribution, i.e., averaging. The assumption regarding the distribution of the fibers can have a
Chapter 6 Technical Discussions 6-65
marked effect on the determination of the material parameters; two of the most commonly postulated distributions are the
square and the hexagonal, with the latter generally considered as being a better representation of randomly distributed
fibers.
The stress-strain relationships, for those sections evaluated as continua, can be written as:
c
aa
= o
aa
/E
L
- (V
L
/E
L
)o
bb
- (V
L
/E
L
)o
cc
c
bb
= -( V
L
/E
L
)o
aa
+ o
bb
/E
T
- (V
T
/E
T
)o
cc
c
cc
= -( V
L
/E
L
)o
aa
- (V
T
/E
T
)o
bb
+ o
cc
/E
T
c
ab
= t
ab
/ 2 G
L
c
bc
= t
bc
/ 2 G
T
c
ac
= t
ac
/ 2 G
L
Where:
c
ij
= strain along direction i on face j
o
ij
, t
ab
= stress (normal, shear) along direction i on face j
E
L
= modulus of elasticity of laminate layer in longitudinal direction
V
L
= Poissons ratio of laminate layer in longitudinal direction
E
T
= modulus of elasticity of laminate layer in transverse direction
V
T
= Poissons ratio of laminate layer in transverse direction
G
L
= shear modulus of elasticity of laminate layer in longitudinal direction
G
T
= shear modulus of elasticity of laminate layer in transverse direction
These relationships require that four modules of elasticity (E
L
, E
T
, G
L
, and G
T
) and two Poissons ratios (V
L
and V
T
) to be
evaluated for the continuum. Extensive research (References 4 - 10) has been done to estimate these parameters. There is
general consensus that the longitudinal terms can be explicitly calculated; for cases where the fibers are significantly stiffer
than the matrix, they are:
E
L
= E
F
| + E
M
(1 - |)
G
L
= G
M
+ |/ [ 1 / (G
F
- G
M
) + (1 - |) / (2G
M
)]
V
L
= V
F
| + V
M
(1 - |)
Parameters in the transverse direction cannot be calculated; only their upper and lower bounds can. Correlations with
empirical results have yielded approximations (Reference 5 and 6):
G
T
= G
M
(1 + 0.6\|) / [(1 - |)
1.25
+ | (G
M
/G
F
)]
V
T
= V
L
(E
L
/ E
T
)
Use of these parameters permits the development of the homogeneous material models which facilitate the calculation of
longitudinal and transverse stresses acting on a laminate layer. The resulting stresses may be allocated to the individual
fibers and matrix using relationships developed during the micro analysis.
6-66 Technical Discussions
Macro-Level Analysis
Where Mini-level analysis provides the means of evaluation of individual laminate layers, Macro-level analysis provides the
means of evaluating components made up of multiple laminate layers. It is based upon the assumption that not only the
composite behaves as a continuum, but that the series of laminate layers acts as a homogeneous material with properties
estimated based on the properties of the layer and the winding angle, and that finally, failure criteria are functions of the
level of equivalent stress.
Laminate properties may be estimated by summing the layer properties (adjusted for winding angle) over all layers. For
example
Where:
ELAM|| = Longitudinal modulus of elasticity of laminate
tLAM = thickness of laminate
Ek = Longitudinal modulus of elasticity of laminate layer k
C
i
k = transformation matrix orienting axes of layer k to longitudinal laminate axis
Cjk = transformation matrix orienting axes of layer k to transverse laminate axis
tk = thickness of laminate layer k
Once composite properties are determined, the component stiffness parameters may be determined as though it were made
of homogeneous material i.e., based on component cross-sectional and composite material properties
Normal and shear stresses can be determined from 1) forces and moments acting on the cross-sections, and 2) the cross-
sectional properties themselves. These relationships can be written as
o
aa
= F
aa
/ A
aa
M
ba
/ S
ba
M
ca
/ S
ca
o
bb
= F
bb
/ A
bb
M
ab
/ S
ab
M
cb
/ S
cb
o
cc
= F
cc
/ A
cc
M
ac
/ S
ac
M
bc
/ S
bc
t
ab
= F
ab
/ A
ab
M
bb
/ R
ab
Chapter 6 Technical Discussions 6-67
t
ac
= F
ac
/ A
ac
M
cc
/ R
ac
t
ba
= F
ba
/ A
ba
M
aa
/ R
ba
t
bc
= F
bc
/ A
bc
M
cc
/ R
bc
t
ca
= F
ca
/ A
ca
M
aa
/ R
ca
t
cb
= F
cb
/ A
cb
M
bb
/ R
cb
Where:
o
ij
= normal stress along axis i on face j
F
ij
= force acting along axis i on face j
A
ij
= area resisting force along axis i on face j
M
ij
= moment acting about axis i on face j
S
ij
= section modulus about axis i on face j
t
ij
= shear stress along axis i on face j
R
ij
= torsional resistivity about axis i on face j
Using the relationships developed under macro, mini, and micro analysis, these stresses can be resolved back into local
stresses within the laminate layer, and from there, back into stresses within the fiber and the matrix. From these, the failure
criteria of those microscopic components, and hence, the component as a whole, may be checked.
Implementation of Macro-Level Analysis for Piping Systems
The macro-level analysis described above is the basis for the preeminent FRP piping codes in use today, including Code BS
7159 (Design and Construction of Glass Reinforced Plastics Piping Systems for Individual Plants or Sites) and the
UKOOA Specification and Recommended Practice for the Use of GRP Piping Offshore.
BS 7159 uses methods and formulas familiar to the world of steel piping stress analysis in order to calculate stresses on the
cross-section, with the assumption that FRP components have material parameters based on continuum evaluation or test.
All coincident loads, such as thermal, weight, pressure, and axial extension due to pressure need be evaluated
simultaneously. Failure is based on the equivalent stress calculation method; since one normal stress (radial stress) is
traditionally considered to be negligible in typical piping configurations, this calculation reduces to the greater of (except
when axial stresses are compressive):
S
eq
S
x
2
4t
2
+ =
(when axial stress is greater than hoop)
S
eq
S
h
2
4t
2
+ =
(when hoop stress is greater than axial)
A slight difficulty arises when evaluating the calculated stress against an allowable, due to the orthotropic nature of the FRP
piping normally the laminate is designed in such a way to make the pipe much stronger in the hoop, than in the
longitudinal, direction, providing more than one allowable stress. This is resolved by defining the allowable in terms of a
design strain ed, rather than stress, in effect adjusting the stress allowable in proportion to the strength in each direction
i.e., the allowable stresses for the two equivalent stresses above would be (ed ELAMX) and (ed ELAMH) respectively. In
lieu of test data, system design strain is selected from Tables 4.3 and 4.4 of the Code, based on expected chemical and
temperature conditions.
6-68 Technical Discussions
Actual stress equations as enumerated by BS 7159 display below:
1 Combined stress: straights and bends:
oC = (of
2
+ 4oS
2
)
0.5
s cd ELAM
or
oC = (oX
2
+ 4oS
2
)
0.5
s cd ELAM
Where:
oC = combined stress
oR = circumferential stress
=oRP + oRB
oS =torsional stress
= MS(Di + 2td) / 4I
oX = longitudinal stress
= oXP + oXB
oRP = circumferential pressure stress
= mP(Di + td) / 2 td
oRB = circumferential bending stress
= [(Di + 2td) / 2I] [(Mi SIFRi)
2
+ Mo SIFRo)
2
]
0.5
(for bends, = 0 for straights)
MS = torsional moment on cross-section
D = internal pipe diameter
td = design thickness of reference laminate
I = moment of inertia of pipe
m = pressure stress multiplier of component
P = internal pressure
Mi = in-plane bending moment on cross-section
SIFRi= circumferential stress intensification factor for in-plane moment
M = out-plane bending moment on cross-section
SIFR = circumferential stress intensification factor for out-plane moment
oXP = longitudinal pressure stress
= P(Di + td) / 4 td
oXB = longitudinal bending stress
= [(Di + 2td) / 2I] [(Mi SIFxi)
2
+ Mo SIFxo)
2
]
0.5
SIF = longitudinal stress intensification factor for in-plane moment
SIF = longitudinal stress intensification factor for out-plane moment
2 Combined stress: branch connections:
oCB = ((oRP + obB)
2
+ 4oSB
2
)
0.5
ed ELAM
Where:
Chapter 6 Technical Discussions 6-69
oCB = branch combined stress
oRP = circumferential pressure stress
= mP(Di + tM) / 2 tM
obB = non-directional bending stress
= [(Di + 2td) / 2I] [(Mi SIFBi)
2
+ Mo SIFBo)
2
]
0.5
oSB = branch torsional stress
= MS(Di + 2td) / 4I
tM = thickness of the reference laminate at the main run
SIFBi = branch stress intensification factor for in-plane moment
SIFB = branch stress intensification factor for out-plane moment
3 When longitudinal stress is negative (net compressive):
oR - Vfx ox s c ELAMR
Where:
Vfx = Poissons ratio giving strain in longitudinal direction caused by stress in circumferential direction
cR = design strain in circumferential direction
ELAMR = modulus of elasticity in circumferential direction
BS 7159 also dictates the means of calculating flexibility and stress intensification (k- and i-) factors for bend and tee
components, for use during the flexibility analysis.
6-70 Technical Discussions
BS 7159 SIF Factors for Bends
Chapter 6 Technical Discussions 6-71
BS 7159 imposes a number of limitations on its use, the most notable being the limitation of a system to a design pressure
of 10 bar, the restriction to the use of designated design laminates, and the limited applicability of the k- and i- factor
calculations to pipe bends (i.e., mean wall thickness around the intrados must be 1.75 times the nominal thickness or less).
BS 7159 SIF Factors for Tees
This code appears to be more sophisticated, yet easy to use, than any available alternative, so it is recommended here that its
calculation techniques be applied even to FRP systems outside its explicit scope, with the following recommendations:
Pressure stiffening of bends should be based on actual design pressure, rather than allowable design strain.
Design strain should be based on manufacturers test and experience data wherever possible (with consideration for
expected operating conditions).
Fitting k- and i- factors should be based on manufacturers test or analytic data if available.
The UKOOA Specification is similar in many respects to the BS 7159 Code, except that it simplifies the calculational
requirements in exchange for imposing more limitations and more conservatism on the piping operating conditions.
Rather than explicitly calculating a combined stress, the specification defines an idealized envelope of combinations of axial
and hoop stresses which cause the equivalent stress to reach failure. This curve represents the plot of:
6-72 Technical Discussions
(ox / ox-all)
2
+ (ohoop / ohoop-all)
2
- [ox ohoop / (ox-all ohoop-all)] s 1.0
Where:
ox-all = allowable stress, axial
ohoop-all = allowable stress, hoop
The Specification conservatively limits the user to that part of the curve falling under the line between ox-all (also known as
sa(0:1)) and the intersection point on the curve where ohoop is twice sx-(a natural condition for a pipe loaded only with
pressure), as shown in the following figure.
An implicit modification to this requirement is the fact that pressure stresses are given a factor of safety (typically equal to
2/3) while other loads are not. This gives an explicit requirement of
Pdes s f1 f2 f3 LTHP
Where:
Pdes = allowable design pressure
f1 = factor of safety for 97.5% lower confidence limit, usually 0.85
f2 = system factor of safety, usually 0.67
f3 = ratio of residual allowable, after mechanical loads
= 1 - (2 oa
b
) / (r f1 LTHS)
oa
b
= axial bending stress due to mechanical loads
r = oaa(0:1) / oa(2:1)
oa(0:1)
b
= long term axial tensile strength in absence of pressure load
oa(2:1) = long term axial tensile strength under only pressure loading
LTHS = long term hydrostatic strength (hoop stress allowable)
LTHP = long term hydrostatic pressure allowable
Note: This has been implemented in the CAESAR II pipe stress analysis software as:
Code Stress Code Allowable
oa
b
(f2 /r) + PDm / (4t)
s (f1 f2 LTHS) / 2.0
Chapter 6 Technical Discussions 6-73
Where:
P = design pressure
D = pipe mean diameter
t = pipe wall thickness
and i-factors for bends are to be taken from the BS 7159 Code, while no such factors are to be used for
tees.
The UKOOA Specification is limited in that shear stresses are ignored in the evaluation process; no consideration is given
to conditions where axial stresses are compressive; and most required calculations are not explicitly detailed.
FRP Analysis Using CAESAR II
Practical Applications
CAESAR II has had the ability to model orthotropic materials such as FRP almost since its inception. It also can specifically
handle the requirements of the BS 7159 Code and the UKOOA Specification.
FRP material parameters corresponding to those of many vendors lines are provided with CAESAR II and may be pre-
selected by the user to be the default values whenever FRP piping is used. Other options, as to whether the BS 7159
pressure stiffening requirements should be carried out using design strain or actual strain can be set in CAESAR IIs con-
figuration module as well.
FRP Properties Tab - Configuration Setup Dialog
6-74 Technical Discussions
Special Execution Parameters for Activating the Orthotropic Material Model
Selecting material 20 Plastic (FRP) activates CAESAR IIs orthotropic material model and brings in the appropriate
material parameters from the pre-selected materials. The orthotropic material model is indicated by the changing of two
fields from their previous isotropic values: Elastic Modulus (C) > Elastic Modulus/axial and Poisson's Ratio >
Ea/Eh*Vh/a. These changes are necessary due to the fact that orthotropic models require more material parameters than
do isotropic. For example, there is no longer a single modulus of elasticity for the material, but now two axial and hoop.
There is no longer a single Poissons ratio, but again two V
h/a
(Poissons ratio relating strain in the axial direction due to
stress-induced strain in the hoop direction) and V
a/h
(Poissons ratio relating strain in the hoop direction due to stress-
induced strain in the axial direction). Also, unlike isotropic materials, the shear modulus does not follow the relationship G
= 1 / E (1-V), so that value must be explicitly input as well.
Chapter 6 Technical Discussions 6-75
Example Orthotropic Parameters Required in Piping Input
In order to minimize input, a few of these parameters can be combined, due to their use in the program. Generally, the only
time that the modulus of elasticity in the hoop direction, or the Poissons ratios are used during flexibility analysis is when
calculating piping elongation due to pressure (note that the modulus of elasticity in the hoop direction is used when
determining certain stress allowables for the BS 7159 code):
d
x
= (o
x
/ E
a
- V
h/a
* o
hoop
/ E
h
) L
Where:
d
x
= extension of piping element due to pressure
o
x
= longitudinal pressure stress in the piping element
E
a
= modulus of elasticity in the axial direction
V
h/a
= Poissons ratio relating strain in the axial direction due to stress-induced strain in the hoop
direction
o
hoop
= hoop pressure stress in the piping element
E
h
= modulus of elasticity in the hoop direction
6-76 Technical Discussions
L = length of piping element
This equation can be rearranged, to require only a single new parameter, as
d
x
= (o
x
- o
hoop
* (E
a
/ E
h
* V
h/a
)) * L / E
a
Note: In theory, that single parameter, (E
a
/ E
h
* V
h/a
) is identical to V
a/h
.
The shear modulus of the material is required in ordered to develop the stiffness matrix; in CAESAR II, this value, expressed
as a ratio of the axial modulus of elasticity, is brought in from the pre-selected material, or can be changed on a problem-
wise basis using the special execution parameter screen accessed by the Environment menu from the piping spreadsheet
(see figure). This screen also shows the coefficient of thermal expansion (extracted from the vendor file or entered by the
user) for the material, as well as the default laminate type, as defined by the BS 7159 Code:
Type 1 All chopped strand mat (CSM) construction with an internal and an external surface tissue reinforced layer.
Type 2 Chopped strand mat (CSM) and woven roving (WR) construction with an internal and an external surface
tissue reinforced layer.
Type 3 Chopped strand mat (CSM) and multi-filament roving construction with an internal and an external surface
tissue reinforced layer.
The latter is used during the calculation of flexibility and stress intensification factors for piping bends.
Bend and tee information may be entered easily through use of auxiliary spreadsheets. Bend radius and laminate type may
be changed on a bend by bend basis, as shown in the corresponding figure. BS 7159 fabricated and moulded tee types are
specified by defining CAESAR II tee types 1 and 3 respectively at intersection points. CAESAR II automatically calculates the
appropriate flexibility and stress intensification factors for these fittings as per code requirements.
Required code data may be entered on the Allowables auxiliary spreadsheet; with the program providing fields for CODE
(both number 27 BS 7159 and 28 UKOOA are available). After selection of BS 7159, CAESAR II provides fields for
entry of the following code parameters:
Chapter 6 Technical Discussions 6-77
SH1,2,3 = longitudinal design stress = c
d
E
LAMX
Kn1,2,3 = cyclic reduction factor (as per BS 7159 paragraph 4.3.4)
E
h
/E
a
= ratio of hoop modulus of elasticity to axial modulus of elasticity
K = temperature differential multiplier (as per BS 7159 paragraph 7.2.1)
6-78 Technical Discussions
After selection of UKOOA, CAESAR II provides fields for entry of the following code parameters:
SH1,2,3 = hoop design stress = f
1
* LTHS
R1,2,3 = ratio r (o
a(0:1)
/ o
a(2:1)
)
f
1
= system factor of safety (defaults to 0.67 if omitted)
K = temperature differential multiplier (same as BS 7159)
These parameters need only be entered a single time, unless they change at some point in the system.
Performing the analysis is even simpler than the system modeling. CAESAR II evaluates the operating parameters and
automatically builds the appropriate load cases; in this case three are built:
Operating (includes pipe and fluid weight, temperature, equipment displacements, pressure, etc.). This case is used to
determine maximum code stress/strain, operational equipment nozzle and restraint loads, hot displacements, etc.
Cold (same as above, except excluding temperature and equipment movements). This case is used to determine cold
equipment nozzle and restraint loads.
Expansion (cyclic stress range between the cold and hot case). This case may be used to evaluate fatigue criteria as per
paragraph 4.3.4 of the BS 7159 Code.
After analyzing the response of the system under these loads, CAESAR II presents the user with a menu of possible output
reports. Reports may be designated by selecting a combination of load case and results type (displacements, restraint loads,
element forces and moments, and stresses). From the stress report, the user can determine at a glance whether the system
passed or failed the stress criteria.
For UKOOA code, the piping is considered to be within allowables when the operating stress falls within the idealized
stress envelope (indicated by the straight line in the following figure).
Chapter 6 Technical Discussions 6-79
Conclusion
A reliable, powerful, yet easy to use, pipe stress analysis program with world wide acceptance is now available for
evaluation of FRP piping systems as per the requirements of the most sophisticated FRP piping codes. This means that
access to the same analytical methods and tools long enjoyed by engineers using steel pipe is available to any potential user
of FRP piping ensuring that design.
References
1 Cross, Wilbur, An Authorized History of the ASME Boiler an Pressure Vessel Code, ASME, 1990
2 Olson, J. and Cramer, R., Pipe Flexibility Analysis Using IBM 705 Computer Program MEC 21, Mare Island Report
277-59, 1959
3 Fiberglass Pipe Handbook, Composites Institute of the Society of the Plastics Industry, 1989
4 Hashin, Z., Analysis of Composite Materials a Survey, Journal of Applied Mechanics, Sept. 1983
5 Greaves, G., Fiberglass Reinforced Plastic Pipe Design, Ciba-Geigy Pipe Systems
6 Puck, A. and Schneider, W., On Failure Mechanisms and Failure Criteria of Filament-Wound Glass-Fibre/Resin
Composites, Plastics and Polymers, Feb. 1969
7 Hashin, Z., The Elastic Moduli of Heterogeneous Materials, Journal of Applied Mechanics, March 1962
8 Hashin, Z. and Rosen, B. Walter, The Elastic Moduli of Fibre Reinforced Materials, Journal of Applied Mechanics,
June 1964
9 Whitney, J. M. and Riley, M. B., Elastic Properties of Fiber Reinforced Composite Materials, AIAA Journal, Sept.
1966
6-80 Technical Discussions
10 Walpole, L. J., Elastic Behavior of Composite Materials: Theoretical Foundations, Advances in Applied Mechanics,
Volume 21, Academic Press, 1989
11 BS 7159: 1989 British Standard Code of Practice for Design and Construction of Glass Reinforced Plastics (GRP)
Piping Systems for Individual Plants or Sites
12 UK Offshore Operators Association Specification and Recommended Practice for the Use of GRP Piping Offshore
1994
Chapter 6 Technical Discussions 6-81
Code Compliance Considerations
General Notes for All Codes
This section comprises general notes that cover code compliance. The first several pages contain information that applies to
all of the codes. The last pages contain code-specific discussions. The user is urged to review the general notes once,
highlighting those that apply to his specific type of problem. He is also recommended to review the notes for the particular
piping code to be used.
Chapter 2 (see "Configuration and Environment" on page 2-1) of the Technical Reference Manual gives details about the
various parameters that can be used in the CAESAR II setup file. Many of these parameters are discussed from an
application point-of-view in the text that follows. Users not familiar with the setup file should see Chapter 2 (see
"Configuration and Environment" on page 2-1) of the Technical Reference Manual.
An SIF of 2.3 is used for threaded joints for all codes. An SIF of 1.2 is used for double welded slip-on flanges for all codes.
An SIF of 1.6 is used for lap joint flanges with B16.9 stub ends for all codes.
The only piping codes that cannot take advantage of the WRC 329 options, or the option to use the ASME NC and ND rules
for reduced intersections, are BS806 and the Swedish Power Method 1. These codes have no provision for using the
effective section modulus, and any extrapolation of the ASME methods into these codes at this time is considered
unwarranted.
The Weld ID on the SIF & TEE Auxiliary field is used in the calculation of the Bonney Forge Sweepolet and Bonney
Forge Insert Weldolet. If the user can be sure that the welds for these fittings will be finished or dressed, then the
specification of the Weld ID will result in lower stress intensification factors.
Bend SIF overrides by the user affect the entire cross section of the bend, and as such cannot be specified for only a single
point on the bend curvature. The users defined SIF should be specified for the bend TO node. CAESAR II will then apply
this SIF, (in place of the codes SIF) over the entire bend curvature, i.e. from weldline to weldline.
The default fiberglass-reinforced plastic (FRP) bend and intersection SIF is 2.3. This value is used for all bends and for all
intersections unless otherwise modified by the user. Flexibility factors for FRP bends are 1.0. Users modifying these values
are cautioned that SIFs generated from steel fatigue tests may not be applicable as a basis for SIFs for FRP fittings.
At this time stress intensification factors cannot be less than 1.0. Because original SIF work used girth butt welds as a basis,
some manufacturers are generating SIFs for their fittings that are less than 1.0 implying that the fitting is stronger than a
girth butt weld. CAESAR II does not permit the use of these reduced SIFs at this time.
The REDUCED_INTERSECTION calculations discussed at length in the following text apply whenever d/D < 0.975.
Where (d) is the outside diameter of the branch, and (D) is the outside diameter of the header.
WRC 329 for the codes: B31.3, B31.4, B31.11, and B31.1 (1967) does the following:
1 Include torsional stresses in all stress calculations, (i.e. Sustained and Occasional)
2 Use a torsional SIF of (r/R) io.
3 Compute i(ib) from: 0.6(R/T)**2/3 [1+0.5(r/R)**3](r/rp)
4 For i(ob) use 1.5(R/T)**2/3 (r/R)**1/2 (r/rp), and i(ob)(t/T)>1.5
when (r/R) < 0.9., use 0.9(R/T)**2/3 (r/rp), and i(ob)(t/T)>1.0
when (r/R) = 1.0, and use interpolation when 1.0 > (r/R) > 0.9
5 For ir use 0.8 (R/T)**2/3 (r/R), and ir > 2.1
6-82 Technical Discussions
6 If a radius at the junction is provided greater than the larger of t/2 or T/2, then the calculated SIFs may be divided by
2.0, but with ib>1.5 and ir>1.5.
WRC 329/330 for the codes: B31.1, B31.8, ASME III NC & ND, Navy 505, Z183, Z184, and Swedish Method 2, do the
following:
1 For ib, use 1.5(R/T)**2/3 (r/R)**1/2 (r/rp), and ib(t/T)>1.5
when (r/R) < 0.9.
use 0.9(R/T)**2/3 (r/rp), and ib(t/T)>1.0
when (r/R) = 1.0, and
use interpolation when 1.0 > (r/R) > 0.9
2 For ir, use 0.8 (R/T)**2/3 (r/R), and ir > 2.1
3 If a radius at the junction is provided greater than the larger of t/2 or T/2, then the calculated SIFs may be divided by
2.0, but with ib>1.5 and ir>1.5.
Bonney Forge Sweepolets tend to be a little more conservative because they are used for fittings in the Nuclear industry.
The Bonney Forge Sweepolet equations can generate SIFs less than one because they are stronger than the girth butt weld
used as the unity basis for the code fitting SIFs. CAESAR II does not permit SIFs of less than 1.0. If a Bonney Forge
Sweepolet SIF is generated that is less than 1.0, 1.0 will be used.
Even though CAESAR II allows the specification of two element intersections, the user cannot specify two SIFs at a single
node and get an increased SIF. For example a socketweld SIF and an intersection SIF cannot be specified at the same point.
For two element joints the largest diameter and the smallest T is used when discrepancies exist between the two adjoining
pipes. When the two element fitting is a socket weld then the largest T is used. These selections are made to generate the
largest SIFs and thus the most conservative stress calculations for under specified fittings.
Note: The mismatch given for girth butt welds is the average mismatch and not the maximum mismatch. Users must
make sure that any maximum mismatch requirements are satisfied themselves.
If a fillet leg is given in conjunction with a socket weld SIF definition, then both socket weld types result in the same SIF.
The B31.3 sustained case SIF factor in the setup file affects all of the following codes: B31.4, B31.8, B31.11, Navy 505,
Z662, and B31.1 (1967). The default for the B31.3_SUS_CASE_SIF_FACTOR=1.0.
The calculation for the corroded effective section modulus is made from (pi)(r
2
)te where (r) is the average cross sectional
radius of the non-corroded pipe and (te) is the corroded thickness. The thickness (te) is selected based on the noncorroded
thicknesses of the branch and header, i.e. the lesser of Th and iTb. The resulting value has the corrosion subtracted from it
before the effective section modulus calculation is made.
The Maximum Shear Stress is always calculated with the corroded wall thickness, regardless of the setting of the
ALL_STRESS_CASES_CORRODED flag in the setup file.
If different piping codes are used in one job the code reported at the top of the output stress report will be the code that was
last encountered during model input. SIFs, allowables and code equations are all computed in accordance with the code that
is varying with the input.
The following piping codes do not, by default, include torsion in the sustained or occasional stress calculations:
B31.3 Navy 505
B31.4 Z662
B31.8 B31.1 (1967)
B31.11 GPTC/Z380
Chapter 6 Technical Discussions 6-83
Torsion is not added because these codes instruct the user to add the longitudinal stresses due to weight, pressure and
other sustained loadings. Torsional shear stresses are not longitudinal stresses. The user can request that torsion be added
into the sustained and occasional stress equations by putting the parameter: ADD_TORSION_IN_SL_STRESS=YES in the
setup file. The torsion stress is still however not intensified, as it is in the power piping codes. This lack of intensification is
considered an oversight, and is corrected in WRC 329. The user can implement this fix in his running of any of the above
codes by putting the parameter: USE_WRC330 in the setup file.
Note that the radius given in CAESAR II is always the equivalent closely spaced miter radius. The radius calculation given
for widely spaced miters in the piping codes is only to be used when the user breaks the widely spaced miter bend down into
individual single cut miters as recommended.
B31.1 and the ASME Section III piping codes provide stress intensification factors for reduced branch ends. None of the
other piping codes provide these SIFs. The REDUCED INTERSECTION=<option> parameter in the setup file allows the
user of other piping codes to access these improved SIFs for reduced fittings. Users taking advantage of this option should
review the notes associated with the B31.1 and the ASME Section III codes that follow to make sure that any other
parameters or input associated with the reduced intersection calculations are set as necessary.
When the user requests pressure stiffening for those codes that do not normally provide it, the pressure stiffening is applied
for all bends and for both miter types.
The defaults for the occasional load factor from the setup file used in the evaluation of the allowable stress, is given in the
text that follows for each of the piping codes.
B31.1: The occasional load factor is 1.15.
B31.3: The occasional load factor is 1.33.
B31.4: This is 0.8Sy as defined in the most recent edition of B31.4. OCC does not affect a B31.4 analysis in CAESAR II.
B31.5: The occasional load factor is 1.33.
B31.8: An occasional case is not specifically defined. If the user enters an OCC load case the allowable will default to
1.0 times the sustained allowable stress, i.e. OCC=1.0
B31.11: This is 0.88Sy as defined in the most recent edition of B31.11 OCC does not affect a B31.11 analysis in
CAESAR II.
ASME Section III NC and ND: The default value of OCC is 1.2 so, the occasional stress allowable is 1.8 (1.2 X 1.5) Sh
but not greater than 1.5 Sy. If OCC is set to 1.5 or 2.0, the allowable is set to the minimum of 2.25 Sh/1.8 Sy (Level C)
or 3.0 Sh/2.0Sy (Level D). Note in the latter two cases, Sm should be entered for Sh.
Navy 505: Occasional cases are not addressed but will default to the method used in B31.1, and an OCC value of 1.15
will be used as the default.
Z662: Occasional cases not defined, but if entered by the user the allowable for the case will default to 1.0 times the
sustained allowable.
BS806: The occasional load case is not defined. If entered the allowable stress for the OCC load case will be K Sh, (the
occasional load factor times the sustained allowable). The default for k is 1.0.
Swedish Method 1: OCC is not used. The load cases are not differentiated. The same allowable Sigma(ber)/1.5 is used
for all load cases.
Swedish Method 2: An OCC default of 1.2 as recommended in the Swedish Piping Code is used.
B31.1(1967): OCC default is 1.15.
Stoomwezen: OCC default is 1.2.
RCC-M C&D: OCC default is 1.2.
CODETI: OCC default is 1.15.
NORWEGIAN: OCC default is 1.2.
FBDR: OCC default is 1.15
BS 7159: The occasional load case is not defined.
6-84 Technical Discussions
UKOOA: The occasional load case is not defined.
IGE/TD/12: Occasional stress increases are addressed is Table 4 of the code. The occasional factor in the setup file has
no bearing on this code.
EN-13480: The occasional load factor varies from 1.0 to 1.8, depending on the loading. Refer to Section 12.3.3 for
details.
GPTC/Z380: An occasional case is not specifically defined. If the user enters an OCC load case the allowable will
default to 1.0 times the sustained allowable stress, i.e. OCC=1.0
HPGSL: The occasional load factor is 1.33.
JPI: The occasional load factor is 1.33.
The occasional load factor can be changed from the program defaults via the setup file. The value should be entered in
percent. To get an occasional load factor of 1.5, the user would enter 50.0
Intersections are not FULL intersections in CAESAR II whenever the branch outside diameter is less than 0.975 times the
header outside diameter.
When there are multiple piping codes in the same piping job, and a piping code change occurs at an intersection, if the
intersection is completely defined with three pipes framing into the intersection then the piping code used to generate the
SIF equations will be that one associated with the first header pipe framing into the intersection. If the intersection is only
partially defined, then the piping code will be selected from the first pipe framing into the intersection point.
The material, thermal expansion, and modulus of elasticity data are for the B31 piping codes. Users may enter their own
material and thermal expansion properties if desired.
There is a small difference between USE_WRC330 and REDUCED_INTERSECTION =WRC330. The first applies for all
full and reduced intersections that are not welding tees or reinforced tees. The latter applies only for reduced fittings that are
not welding tees or reinforced fabricated tees. A fitting is reduced when d/D is less than 0.975.
The Bonney Forge SIF Data came from the technical flyer: Bonney Forge Stress Intensification Factors Bulletin 789/SI-1,
Copyright 1976.
The ASME piping codes primarily combine moments for thermal expansion stresses. When there is any tendency for large
axial forces to exist in the pipe these code equations are not adequate. An example of this is for a buried, or partially buried
pipe. Here the axial stresses can be very high. B31.4 directs the user to compute a longitudinal stress for completely
restrained pipe. CAESAR II allows the user to specify just how much of the pipe is buried. This longitudinal stress is then
added to the stress calculations for thermal and will contribute to a failure prediction that might have otherwise been
ignored. Similar effects can be achieved in CAESAR II by using the axial soil restraint and telling the setup file to include
F/A components in the stress calculations. Users should be aware that for any type of problem, if large axial loads are
developed because of the design, the piping code may not be adequately considering it.
Code-Specific Notes
B31.1
Pressure stiffening is implemented by default. Users may deactivate pressure stiffening for B31.1 runs by entering the
parameter USE_PRESSURE_STIFFENING=NO in the setup file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
B31.1 does not by default add F/A into the stress calculation. F/A and the pressure stresses are added to the bending stress
(whether the tensile or compressive component of bending), to produce the largest longitudinal stress component. This is
true for all codes insofar as the addition of axial and pressure terms are concerned. The user can cause CAESAR II to include
the axial force terms into the code stress by inserting the parameter ADD_F/ A_IN_STRESS=YES to the setup file. The
F/A forces discussed here are structural forces developed in the piping independent of pressure PD/4t forces.
Chapter 6 Technical Discussions 6-85
In 1980 B31.1 added a reduced branch stress intensification factor equation to Appendix D. This equation came directly
from ASME Section III. B31.1 continued however to use the effective section modulus calculation for the branch. The
ASME Section III rules clearly stated that the branch section modulus, NOT the effective section modulus should be used
with the new SIF. B31.1s using of the effective section modulus produced unnecessarily high calculated stresses. This error
was corrected in the 1989 version of B31.1. Prior to Version 3.0 CAESAR II users had two options:
Use the pre-1980 version of the B31.1 SIF rules.
Use the very conservative, post-1980 B31.1 SIF rules.
In version 3.0 (and later) these options also exist, except that the section modulus problem is corrected. For users that wish
to run version 3.0 (and later) just like they ran version 2.2, i.e. without the section modulus correction, they can do so by
putting the parameter: B31.1_REDUCED_Z_FIX=NO in the setup file.
The reduced intersection branch SIFs were not intended for reinforced or welding tees. Conservative results are produced,
but the original researchers did not intend for the SIFs to be used for these fittings. The CAESAR II user can disable the
reduced branch fitting calculations for reinforced or welded tees by putting the parameter
NO_REDUCED_SIF_FOR_RFT_AND_WLT in the setup file. This will produce less conservative results, but can, in some
cases be justified.
B31.1 102.3.2 (c) tells the user to divide the allowable stresses coming from the stress tables in Appendix A by the
applicable weld joint factors listed in Para. 102.4.3.
Stress allowables for B31.1 are calculated from:
Expansion Allowable = f [ (1.25/Eff)(Sc+Sh) - Sl ]
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * (Occ)
Where:
f = Cyclic reduction factor
Eff = Longitudinal Weld Joint Efficiency
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Sl = Sustained Stress
Occ = Occasional Load Factor (Default = 1.15)
Inplane and outplane stress intensification factors for intersections are kept the same in the B31.1 stress calculation.
The B31.1 criteria B length for closely spaced miters is not checked by CAESAR II.
For reducers B31.1 states that the Flexibility Factor is 1.0. The code also states that SIF is: 2.0 max or 0.5 + .01*alpha*
SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end.
Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of the sloped portion of the reducer) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
6-86 Technical Discussions
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Note: Alpha cannot exceed 60 and the larger of D1/t1 and D2/t2 can not exceed 100.
B31.3
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
Inplane and outplane stress intensification factors for intersections are kept separate and unique.
Since the B31.3 piping code gives the equation for the expansion stress explicitly, and since that equation does not include
the longitudinal stress due to axial loads in the pipe, CAESAR II does not include the F/A component of the stress in the
expansion stress equation. (The code also says that the user may wish to add in the F/A component where it may be
significant.) Users can change this by placing the parameter: ADD_F/ A_IN_STRESS=YES to the setup file. The F/A
longitudinal stress component are by default added to the code stress component for all other stress categories.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
No differentiation is made between socket welds with and without undercut. Codes that do differentiate use 1.3 for socket
welds with no undercut, and 2.1 for all others. An SIF of 1.3 is used for all B31.3 socket welds (unless a fillet weld leg
length is specified).
Stress allowables for B31.3 are calculated from:
Expansion Allowable = f [ (1.25/Eff)(Sc+Sh) - Sl ]
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * (Occ)
Where:
f = Cyclic reduction factor
Eff = Weld Joint Efficiency (Only for pre-1980 B31.3)
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Sl = Sustained Stress
Occ = Occasional Load Factor (Default = 1.33)
For B31.3 the flag ALL_STRESS_CASES_CORRODED=NO flag in the setup file returns the corroded stress calculations
to the way they were performed in the 2.2 version of CAESAR II. The corrosion is removed from the sustained and
occasional stress calculations.
See Chapter 2 of the Technical Reference Manual for the setup file parameter B31.3_SUS_CASE_SIF_FACTOR=<nnn>.
This value can have a considerable impact on the sustained case stress calculations.
Pressure effects on miters are allowed in the B31.3 piping code.
For reducers B31.3 states that the Flexibility Factor is 1.0. The code also states that SIF is 1.0.
Chapter 6 Technical Discussions 6-87
B31.4
Pressure stiffening is automatically included as directed per the code. Users may turn pressure stiffening off by including
the parameter USE_PRESSURE_STIFFENING=NO in the setup file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
Inplane and outplane stress intensification factors for intersections are kept separate and unique.
The Allowables for B31.4 are calculated from:
Expansion Allowable = (0.72)(Sy)
Sustained Allowable = (0.75)(0.72)(Sy)
Occasional Allowable = (0.8)(Sy)
Operating Allowable = (0.9)(Sy) if the axial stress is compressive, no code check done if axial
stress tensile
Where:
Sy = Specified Minimum Yield Stress
B31.4 does not use EFF, (found in the Allowable Stress Auxiliary field). The minimum yield stress is all that is required to
compute flexibility stress allowables.
B31.4 has no provision for using an effective section modulus calculation at intersections.
B31.4 does not include a provision for the liberal allowable. This particular option is not used for B31.4 stress allowable
calculations. The occasional load factor (used in the other piping codes for determining the allowable stress for occasional
load sets) is not used in B31.4, as the allowable stress is expressly given as 0.8 times the minimum yield stress.
CAESAR II assumes that 419.6.4(b) establishes a requirement for the allowable operating stress at 90% of Sy; when the net
axial stress is compressive (i.e., when longitudinal pressure stresses can be ignored in underground pipes). The last sentence
in the paragraph establishes that: Beam bending stresses shall be included in the longitudinal stress for those portions of the
restrained line which are supported above ground. CAESAR II users have two options for including this axial stress in their
analyses:
1 Include axial friction restraints and include the ADD_F/A parameter into the setup file. Set the fac value to 0.001 to
indicate that the line is buried, so longitudinal pressure stresses are not present, so the hoop stress component must be
considered.
2 Use the fac value to have CAESAR II compute the axially-restrained stress and include it during stress calculations.
If a nonzero fac value is entered, the pressure plus axial loads in the pipe are multiplied by (1-Fac). This gives a more
realistic estimation of the axial stress in the pipe when the user has included both of the effects above.
Users should note that paragraph 419.6.4(b) requires 1) the reduction of the axial expansion stress by the product of
Poissons ratio and the pressure hoop stress, and 2) the addiction of the hoop stress to the axial stress. The latter represents
the calculation of stress intensity when the axial stress is compressive, implying that there is no longitudinal pressure stress
in buried pipe (the pressure loads are transmitted directly to the soil). CAESAR II handles this case in the Operating Load
Case, where the hoop stress is added in and the allowable stress is set to 0.9 Sy whenever the axial stress is compressive. If
fac is set to 0.001, the piping element is considered to be buried, so the longitudinal pressure stress is replaced by the
product of Poissons ratio and the hoop stress, in keeping with the spirit of paragraph 419.6.4(b). fac is automatically set
to 0.001 when B31.4 pipe is sent through CAESAR II's buried pipe modeler. The stress due to axial force will also be
included for these elements.
6-88 Technical Discussions
The fac variable should probably not be set to 1.0 with B31.4 and thermal expansion cases where the user is going from
one thermal state to another state, i.e. where the case is of the form: DS1-DS2, and both DS1 and DS2 contain temperatures.
In this case the thermal expansion used in the restrained pipe calculation comes from the last thermal specified in the load
case definition. In the example above the thermal expansion associated with the DS2 load case.
The base hoop stress on OD flag in the setup file is used by B31.4 when the hoop stress is calculated for the restrained pipe
longitudinal stress calculation. The default is to base the hoop stress calculation on the average diameter, and the equation
PD/2t. In the mechanical stress calculations the hoop stress is based on the inside diameter. (This is the hoop stress that is
printed in the 132 column CAESAR II stress report.)
For reducers B31.4 states that the Flexibility Factor is 1.0. The code also states that SIF is 1.0.
B31.4 Chapter IX
Chapter IX presents the offshore requirements of the B31.4 code.
All Stress Intensification Factors, Flexibility Factors, and section moduli are calculated exactly as in the standard B31.4
Code. Stress calculations are made using the uncorroded wall thickness.
Operating, Sustained, or Occasional load cases are treated identically (there is no provision for a code check for an
Expansion load case, so no Expansion cases are generated under this code). For these load cases, three stress calculations
are done, each with a different allowable. The stress calculation causing the highest percent of allowable is reported in the
stress report, along with its specific allowable. These stress checks are:
Hoop Stress: S
h
s F
1
S
y
Longitudinal Stress: |S
L
| s 0.8 S
y
Equivalent Stress: S
e
s 0.9 S
y
Where:
S
h
= (P
i
P
e
) D / 2t
P
i
= internal pressure
P
e
= external pressure
D = outer diameter
t = wall thickness
F
1
= hoop stress design factor (0.60 or 0.72, see Table A402.3.5(a) of the B31.4 Code)
S
y
= specified minimum yield strength
S
L
= S
a
+ S
b
or S
a
- S
b
, whichever results in greater stress value
S
a
= axial stress (positive tensile, negative compressive)
S
b
= bending stress
S
e
= 2[((S
L
- S
h
)/2)
2
+ S
t
2
]
1/2
S
t
= torsional stress
B31.5
For reducers B31.5 states that the Flexibility Factor is 1.0. The code also states the SIF is 1.0.
Chapter 6 Technical Discussions 6-89
B31.8
The B31.8 stress requirements have been implemented in CAESAR II in the following manner:
Restrained Pipe (as defined in Section 833.1):
For Straight Pipe:
Max(S
L
, S
C
) < 0.9ST (OPE)
Max(S
L
, S
C
) < 0.9ST (SUS)
S
L
< 0.9ST (OCC)*
and
S
C
< ST (OCC) *
* CAESAR II prints the controlling stress of the two
For All Other Components
S
L
< 0.9ST (OPE, SUS, OCC)
Unrestrained Pipe (as defined in Section 833.1):
S
L
< 0.75ST (SUS, OCC)
S
E
< f[1.25(S
C
+ S
H
) S
L
] (EXP)
Where:
S
L
= S
P
+ S
X
+ S
B
S
P
= 0.3S
Hoop
(for restrained pipe); 0.5S
Hoop
(for unrestrained pipe)
S
X
= R/A
S
B
= M
B
/Z (for straight pipe/bends with SIF = 1.0); M
R
/Z (for other components)
S
C
= Max (|S
Hoop
S
L
|, sqrt[S
L
2
S
L
S
Hoop
+ S
Hoop
2
])
M
R
= sqrt[(0.75i
i
M
i
)
2
+ (0.75i
o
M
o
)
2
+ M
t
2
]
S
E
= M
E
/Z
M
E
= sqrt[(0.75i
i
M
i
)
2
+ (0.75i
o
M
o
)
2
+ M
t
2
]
S = Specified Minimum Yield Stress
T = Temperature Derating Factor
S
H
= 0.33S
U
T
S
C
= 0.33S
U
S
U
= Specified Minimum Ultimate Tensile Stress
B31.8 (2003 and later) distinguishes between restrained and unrestrained piping for the purposes of stress computations.
When implementing the B31.8 piping code, it is necessary for the user to define which sections of the piping system are
restrained, as per Code Section 833.1. In general, restrained piping is piping in which the soil or supports prevent axial
displacement of flexure at bends. Conversely, unrestrained piping is piping that is free to displace axially or flex at bends.
Additional details are provided in Section 833.1, and users are urged to consult the Code directly. Processing a B31.8
model through CAESAR II's Buried Pipe Processor will designate the buried sections as restrained.
6-90 Technical Discussions
For restrained pipe, B31.8 specifies that the Operating case stresses should include the thermal axial stress component ST (a
constant stress due to linear thermal expansion) but exclude thermal bending stresses from the S
B
component. Since
CAESAR II cannot after-the-fact segregate internal thermal forces and moments from those of other loads, the thermal axial
stresses will actually be calculated and included as part of SX (as opposed to added as a constant), and thermal bending
stresses will actually be conservatively included in S
B
.
Bending stress S
B
is defined differently for straight pipe or large-radius bends than it is for other components. CAESAR II
resolves the ambiguity of exactly what constitutes a large-radius bend by considering any bend having an SIF of 1.0 as
being a large-radius bend.
The OCC occasional load default for B31.8 is 1.111, and is only applied to the allowable for S
C
(combined stress),
calculated only in straight pipes (i.e., the allowable in this case is ST as opposed to 0.9ST). There is no provision for
increasing (or decreasing) this allowable.
In the case of Occasional Stresses in straight pipes, there are potentially two stresses (S
L
and S
C
) to be compared against two
different allowables. CAESAR II prints only one whichever of the two provides the greater ratio of calculated stress vs.
allowable stress. Users can determine which stress is printed by examining the magnitude of the allowable printed.
Pressure stiffening is automatically included as directed per the code. Users may turn pressure stiffening off by including
the parameter USE_PRESSURE_STIFFENING=NO in the setup file.
Modifications to the Flexibility Factor and Stress Intensification Factor of bends resulting from flanged ends are permitted
by the code.
No differentiation is made between socket welds with and without undercut. An SIF of 2.1 is used for all B31.8 socket
welds, unless a fillet weld leg length is specified.
Use of reducers is subject to the following limitations: 1) alpha (the reducer cone angle) is limited to 60, and 2) the larger
of D1/SQRT(t1) and D2/SQRT(t2) cannot exceed 100 (where D1/t1 and D2/t2 are the diameters and thicknesses of the
large and small ends, respectively).
B31.8 Chapter VIII
Chapter VIII presents the offshore requirements of the B31.8 code.
All Stress Intensification Factors, Flexibility Factors, and section moduli are calculated exactly as in the standard B31.8
Code. Stress calculations are made using the non-corroded wall thickness for the hoop and longitudinal stresses, and using
the corroded thickness for the combined stress.
Operating, Sustained, or Occasional load cases are treated identically (there is no provision for a code check for an
Expansion load case, so no Expansion cases are generated under this code). For these load cases, three stress calculations
are done, with different allowables. The stress calculation causing the highest percent of allowable is reported in the stress
report, along with its specific allowable. These stress checks are:
Hoop Stress: S
h
s F
1
S T
Longitudinal Stress: |S
L
| s 0.8 S
Equivalent Stress: S
e
s 0.9 S
Where:
S
h
= (P
i
P
e
) D / 2t
P
i
= internal pressure
P
e
= external pressure
D = outer diameter
Chapter 6 Technical Discussions 6-91
t = wall thickness
F
1
= hoop stress design factor (0.50 or 0.72, see Table A842.22 of the B31.8 Code)
S = specified minimum yield strength
T = temperature derating factor (see Table 841.116A of the B31.8 Code)
Note: The product of S and T (i.e., the yield stress at operating temperature) is required in the SH field of the CAESAR II
input
S
L
= maximum longitudinal stress (positive tensile, negative compressive)
S
e
= 2[((S
L
- S
h
)/2)
2
+ S
s
2
]
1/2
S
s
= torsional stress
B31.11
Pressure stiffening is automatically included as directed per the code. Users may turn pressure stiffening off by including
the parameter USE_PRESSURE_STIFFENING=NO in the setup file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
Inplane and outplane stress intensification factors for intersections are kept separate and unique.
The Allowables for B31.11 are calculated from:
Expansion Allowable = (0.72)(Sy)
Sustained Allowable = (0.75)(0.72)(Sy)
Occasional Allowable = (0.88)(Sy)
Operating Allowable = (0.9)(Sy) if the axial stress is compressive, no code
check done if the axial stress is tensile
Where:
Sy = Specified Minimum Yield Stress
B31.11 does not use EFF, (found in the Allowable Stress Auxiliary field). The minimum yield stress is all that is required
to compute flexibility stress allowables.
B31.11 has no provision for using an effective section modulus calculation at intersections.
B31.11 does not include a provision for the liberal allowable. This particular option is not used for B31.11 stress allowable
calculations. The occasional load factor (used in the other piping codes for determining the allowable stress for occasional
load sets) is not used in B31.11, as the allowable stress is expressly given as 0.88 times the minimum yield stress.
CAESAR II assumes that 1119.6.4(b) establishes a requirement for the allowable operating stress at 90% of Sy; when the net
axial stress is compressive (i.e., when longitudinal pressure stresses can be ignored in underground pipes). The last sentence
in the paragraph establishes that: Beam bending stresses shall be included in the longitudinal stress for those portions of the
restrained line which are supported above ground. CAESAR II users have two options for including this axial stress in their
analyses:
1 Include axial friction restraints and include the ADD_F/A parameter into the setup file. Set the fac value to 0.001 to
indicate that the line is buried, so longitudinal pressure stresses are not present, so the hoop stress component must be
considered.
6-92 Technical Discussions
2 Use the fac value to have CAESAR II compute the axially-restrained stress and include it during stress calculations.
If a nonzero fac value is entered, the pressure plus axial loads in the pipe are multiplied by (1-Fac). This gives a more
realistic estimation of the axial stress in the pipe when the user has included both of the effects above.
Users should note that paragraph 1119.6.4(b) requires 1) the reduction of the axial expansion stress by the product of
Poissons ratio and the pressure hoop stress, and 2) the addition of the hoop stress to the axial stress. The latter represents
the calculation of stress intensity when the axial stress is compressive, implying that there is no longitudinal pressure stress
in buried pipe (the pressure loads are transmitted directly to the soil). CAESAR II handles this case in the Operating Load
Case, where the hoop stress is added in and the allowable stress is set to 0.9 Sy whenever the axial stress is compressive. If
fac is set to 0.001, the piping element is considered to be buried, so the longitudinal pressure stress is replaced by the
product of Poissons ratio and the hoop stress, in keeping with the spirit of paragraph 1119.6.4(b). fac is automatically set
to 0.001 when B31.11 pipe is sent through CAESAR II's buried pipe modeler. The stress due to axial force will also be
included for these elements.
The fac variable should probably not be set to 1.0 with B31.11 and thermal expansion cases where the user is going from
one thermal state to another state, i.e. where the case is of the form: DS1-DS2, and both DS1 and DS2 contain temperatures.
In this case the thermal expansion used in the restrained pipe calculation comes from the last thermal specified in the load
case definition. In the example above the thermal expansion associated with the DS2 load case.
The base hoop stress on OD flag in the setup file is used by B31.11 when the hoop stress is calculated for the restrained pipe
longitudinal stress calculation. The default is to base the hoop stress calculation on the average diameter, and the equation
PD/2t. In the mechanical stress calculations the hoop stress is based on the inside diameter. (This is the hoop stress that is
printed in the 132 column CAESAR II stress report.)
For reducers B31.11 states that the Flexibility Factor is 1.0. The code also states that the SIF is 1.0.
ASME III Subsections NC and ND
Pressure stiffening is not defined by default in the Code. Users may include pressure stiffening on bends in the analysis by
including the parameter USE_PRESSURE_STIFFENING=YES in the configuration file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
The minimum SIF for reinforced and unreinforced fabricated tees is 2.1.
B1 and B2 are calculated according to ASME NC and ND. Equations used are shown in the Help screens for B1 and B2.
If in the odd situation where the user is using the ASME III piping code, and is running dynamics, and is calling one of the
dynamic case expansions, and has the liberal allowable flag turned on, the liberal allowable request will be ignored, and the
difference between Sh and Sl will not be added to the expansion allowable. This is more of a programming decision than an
interpretation of the piping code or a recommendation for doing dynamic analysis.
Inplane and outplane stress intensification factors are the same for the ASME Section III piping codes.
When using USE_WRC329 with ASME NC or ND, for all intersections that are not welding tees or reinforced fabricated
tees, the approximate section modulus is used for the stress calculations, i.e. pi*r
2
*t. This includes all reduced intersections
and all d/D ratios.
Users that DO NOT wish to use the branch stress intensification factors found in Appendix D of the Code for welding and
reinforced reducing tees, should put the flag: NO_REDUCED_SIF_FOR_RFT_AND_WLT in the setup file.
The allowables for ASME III NC and ND are computed from
Expansion Allowable = f( 1.25Sc + 0.25Sh) + (Sh-Sl)
Sustained Allowable = 1.5Sh (If not at an intersection)
Occasional Allowable = 1.8Sh not greater than 1.5Sy (If OCC=1.2); 2.25Sh not greater than
1.8Sy (If OCC=1.5); 3.0Sh not greater than 2.0Sy (If OCC=2.0)
Chapter 6 Technical Discussions 6-93
Where:
f = Cyclic reduction factor
Sc = Cold Allowable
Sh = Hot Allowable
Sl = Sustained stress from PD/4t+0.75iMb.
Sy = Material Yield Stress
OCC = Occasional factor from the CAESAR II configuration file
For two pipe intersections, i.e. butt welds, socket welds, etc. B1 and B2 factors are 1.0. If the ratio of the average branch to
average run radius is less than 0.5 then the reduced intersection rules are applied to the B1 and B2 calculations regardless of
the intersection type. If the reduced intersection rules do not apply then the rules for butt welded fittings are used, i.e.
B2b = 0.4 * (R/T)**2/3 but not < 1.0,
B2r = 0.5 * (R/T)**2/3 but not < 1.0.
Users can always modify the B1 and B2 values for any node in the SIF&TEE Auxiliary field. B1 and B2 values modified
on an auxiliary field only apply for that element, regardless of whether the node is an intersection or not. When r/R < 0.5 the
following equations are used for B1 and B2:
B2b = 0.50 C2b but not < 1.0,
B2r = 0.75 C2r but not < 1.0,
C2b = 3(R/T)**2/3 (r/R)**1/2 (t/T)(r/rp), but not < 1.5
C2r = 1.15(r/t)**1/4 but not < 1.5.
WRC329 does result in smaller branch SIFs than ASME NC and ND, and the same run SIFs. The branch SIFs are smaller
by a factor of 2. This is when d/D<0.5 and WRC 329 corrects the Mob inconsistency when d/D is between 0.5 and 1. Thus
in the lower ranges of d/D ratios WRC 329 is less conservative than the present codes and in the higher ranges WRC 329 is
more conservative than the present codes.
The Pvar value in the allowable stress spreadsheet is for the DIFFERENCE between the operating pressure and Pmax to be
used in eq 11. This is because of the way the occasional stresses are formed in CAESAR II, i.e. the direct addition of two
stress components. So we are computing the sustained stress (including pressure) and adding it to the occasional stress,
including the stress difference between the operating pressure and the peak pressure that is to be used in the ASME
occasional stress equation 11.
The equations 10 or 11 are satisfied by using as the allowable for the iMc/Z stress as the maximum of either f(1.25Sc +
0.25Sh) or f(1.25Sc + 0.25Sh) + (Sh-Sl) where Sl is the sustained stress as defined by equation 11 as PDo/4tn+0.75iMa/Z.
The CAESAR II approach taken for ASME NC and ND for moment summations at intersections to satisfy equations 8 and 9
is the same as for equations 10 and 11, i.e. the SRSS of the moments at each end of the pipe framing into the intersection is
found. The cumulative moment summation rules for a single intersection as per NB 3683.1 are not adhered to. In addition
the effective section modulus rules of NC and ND are used for all intersection stress calculations, i.e. for equations 8 and 9.
(The NB subsection is used to get the values for B1 and B2 only, and to compute the local flexibility if requested) Because
of this approach in CAESAR II, there is no allowable calculated for intersection points and sustained or occasional loads.
The sustained case SIF factor is not used in the ASME class 2 or 3 calculations.
For reducers NC states that the Flexibility Factor is 1.0. The code also states that SIF is:
2.0 max or 0.5 + .01*alpha* SQRT(D2/t2)
6-94 Technical Discussions
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end. Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of the sloped portion of reducer) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Note: Alpha cannot exceed 60 . The larger of D1/t1 and D2/t2 cannot exceed 100.
B1=.5 if alpha s 30 , 1.0 if 30 < alpha s 60 B2 = 1.0.
For reducers ND states that the Flexibility Factor is 1.0. The code also states that SIF is: 2.0 max or 0.5 + .01*alpha*
SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end.
Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of the sloped portion of the reducer) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Note: There is an error in the code, the code states note 12 however, they meant note 14. Alpha cannot exceed 60 . The
larger of D1/t1 and D2/t2 cannot exceed 100.
B1=.5 if alpha s 30 , 1.0 if 30 < alpha s 60 B2 = 1.0.
CANADIAN Z662
Pressure stiffening is not defined by default in the Code. Users may include pressure stiffening on bends by including the
parameter USE_PRESSURE_STIFFENING=YES in the setup file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
There is no limit in Z662 for the beneficial effect of the pad on an intersection. Most codes limit the pad thickness to 1.5
times the header thickness. For Z662 CAESAR II will not limit the pad thickness.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
Inplane and outplane stress intensification factors for intersections are the same.
No differentiation is made between socket welds with and without undercut. Codes that do differentiate use 1.3 for socket
welds with no undercut, and 2.1 for all others. An SIF of 1.3 is used for all Z662 socket welds (unless a fillet weld leg
length is specified). This code has no provision for using an effective section modulus calculation at intersections.
Chapter 6 Technical Discussions 6-95
The allowable stresses are computed from
Expansion Allowable = (0.72)(Sy)(T)
Sustained Allowable = (Sy)(Fac)(T)(L)
Occasional Allowable = (Sy)(Fac)(T)(Occ)(L)
Operating Allowable = 0.9(Sy)(T) If pipe is buried and axial stress is compressive
= (Sy)(T) If pipe is not buried and axial stress is compressive
Where:
Sy = Specified Minimum Yield Stress
Fac = Construction Design Factor
T = Temperature De-rating Factor
Eff = Longitudinal Weld Joint Efficiency
Occ = Occasional Load Factor (=1.0)
L = Location Factor
CAESAR II assumes that Section 4.6.2 of the Z662 code establishes a requirement for the allowable operating stress of 0.9 x
S x T whenever the net axial stress is compressive in the absence of bending stress, and an allowable operating stress of S x
T when the net axial stress is compressive in the presence of bending stress.
Users should note that Section 4.6.2 requires 1) the reduction of the axial expansion stress by the product of Poissons Ratio
and the pressure hoop stress, and 2) the addition of the hoop stress to the axial stress. The latter represents the calculation of
stress intensity when the axial stress is compressive, implying that there is no longitudinal pressure stress in buried pipe (the
longitudinal pressure thrust loads are transmitted directly to the soil).
CAESAR II handles these requirements, in the OPERATING load case, in the following manner:
1 If FAC is set to 1.0, the implication is that the piping system is fully restrained (in the axial direction) as described in
Section 4.6.2.1, and the operating stress is calculated as:
Sh + E a (T2 - T1) - v Sh < 0.9 S x T
2 If FAC is set to 0.001, the implication is that the piping system is buried, but the soil supports are modeled (rather than
just assumed to be fully rigid). This setting removes the longitudinal pressure stress from the equation (as described
above), takes bending stresses into consideration, as required by Section 4.6.2.2.1. In this case, the operating stress is
calculated as:
Sh +Fax/A + Sb - v Sh < S x T
3 If FAC is set to 0.0, the implication is that the piping system is either not restrained, or is a freely spanning or above
ground portion of a restrained line, as described in Section 4.6.2.2.1. In this case, the longitudinal pressure stress is
restored, so this formula only comes into effect if the net axial stress (including pressure) is compressive, in which case
the operating stress is calculated as:
Sh +Slp + Fax/A + Sb < S x T
4 For those elements for which the net axial stress is longitudinal, no operating code stress check is done.
5 Users should note that CAESAR II does not check for buckling, as required by Section 4.6.2.2.2.
For reducers Z662 states that the Flexibility Factor is 1.0 and the SIF is 1.0.
6-96 Technical Discussions
NAVY 505
Pressure stiffening is not defined by default in the Code. Users may include pressure stiffening on bends in the analysis by
including the parameter USE_PRESSURE_STIFFENING=YES in the setup file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
Navy 505 has no provision for using an effective section modulus calculation at intersections.
Inplane and outplane stress intensification factors for intersections are the same.
Navy 505 has no provision for a liberal allowable, i.e. adding the difference between Sh and Sl to the allowed expansion
stress range. This flag in the control parameter spreadsheet has no affect on 505 runs.
Navy 505 does use Eff in computing the cold and the hot allowable. The use of this parameter is subject to some speculation
however.
Navy 505 has no specific allowable for occasional loads. An occasional load factor, similar to B31.1s will be used, and the
occasional allowable calculated from kSh.
The allowable stresses for Navy 505 are calculated from:
Expansion Allowable = f/Eff(1.25Sc + 0.25Sh)
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * Occ
Where:
f = Cyclic reduction factor
Eff = Joint Efficiency (Not explicitly in the Code)
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Occ = Occasional Load Factor (Default=1.15)
The B31.3_SUS_CASE_SIF_FACTOR can be used for 505 to multiply the stress intensification factors for sustained and
occasional loads to be more in line with the current B31.1 practice.
Chapter 6 Technical Discussions 6-97
BS806
For BS806 the maximum hot stress case is considered to be the operating load case. Operating load case allowables are only
given as per BS806 when the creep rupture strength governs the stress range allowable. See BS806 sect 4.11.2.
BS806 SIFs printed are fti and fto for bends, and Bi and Bo for intersections.
Pressure stiffening is not defined by default in the Code. Users may include pressure stiffening on bends by including the
parameter USE_PRESSURE_STIFFENING=YES in the setup file.
Modifications due to flanged ends are permitted in the code for all bend types. This includes closely and widely spaced
mitered bends.
There is no limit in BS806 to the beneficial effect of the pad on an intersection. Most codes limit the pad thickness to 1.5
times the header thickness. For BS806, CAESAR II will not limit the pad thickness.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
Important When there is more than one thermal case to evaluate, the following note should be read carefully
concerning CAESAR II's application of BS806.
Note: Re: BS806 4.11.3.1 paragraph 2, for sectionalized systems: At this time CAESAR II only makes the moment
summation on a load case by load case basis, and does not take the largest moments for an axis for any combination of load
cases. The CAESAR II method was set up to allow the user to make, and combine the effects of each of the load transients
that the piping system undergoes. This is, for the most part the method used in the B31/ASME piping codes. The BS806
method will be conservative in that it uses what is basically a shakedown approach and computes a single worst case
moment difference. The CAESAR II approach still satisfies the shakedown theory, but computes the moment range for each
different load traversed. The BS806 method of combining the maximum moment range will be more conservative. The
BS806 approach also eliminates the need to know where on the pipe the stress is the highest. In reference to the moment
tables in Appendix F, CAESAR II users can get the moment difference between any two load cases, but not the maximum
moment difference for any of the three moment axes as requested by the sectionalized piping rules. In satisfying 4.11.3.1(a)
CAESAR II uses the moment difference between the cold and the hot case to compute the stress.
Only a single modulus of elasticity can be entered for a single element for each job. Different elements can have different
moduli of elasticity, but that modulus cannot be varied between load cases in the same run, i.e. cold and hot moduli of
elasticity cannot be used in the same run at this time.
For BS806 in 4.11.5.2 the value of n is always taken as 1.0., i.e. all branches are of the non-interacting type. See 4.11.4.2
for the definition of n for interacting branches (n is defined in the fourth paragraph of 4.11.4.2).
6-98 Technical Discussions
The CAESAR II equation modeling of the BS806 SIF curves for bends is shown in the following plots.
The BS 806 allowable stresses are calculated as follows:
Expansion Allowable = lesser of (H)(Sc)+(H)(Sh) <or> (H)(Sc)+F
Sustained Allowable = Sy
Occasional Allowable = (Sy)(Occ)
Operating Allowable = S avg rupture at design temperature
Where:
H = Multiplication Factor (0.9 or 1.0 from CAESAR II)
Sc = 0.2% proof stress at room temperature
Sh = 0.2% proof stress at design temperature
F = Mean stress to failure in design life at design temperature.
Occ = Occasional Load Factor (Default=1.0)
Chapter 6 Technical Discussions 6-99
The pressure calculation at the intersections is made as required in BS806 4.8.5.1 Eq. (17). The pressure stress as per 17 is
computed and then combined with the bending and torsional moments at each of the intersection ends 1, 2 and 3
respectively. The m factor is computed as required with a value of n=1, i.e. for non-interacting intersections.
BS806 does not make mention of reducers for SIF calculations.
Swedish Method 1 and 2
Pressure stiffening is not defined by default in the Swedish Code. Users may include pressure stiffening on bends in the
analysis by including the parameter USE_PRESSURE_STIFFENING=YES in the setup file.
Modifications due to flanged ends are permitted in the code for all bends providing the bend is not a widely spaced miter.
Swedish Method 1 cannot take advantage of the WRC329 recommendations. WRC 329, if requested is ignored.
Swedish Method 1 has no provision for using an effective section modulus calculation at intersections.
Inplane and outplane stress intensification factors for intersections are kept the same.
Swedish Code item 9 is dealt with as a US tapered transition. Also items 10 and 11 in the Swedish table 9:2 correspond to
items 8 and 9 in the CAESAR II nomenclature.
The Allowable Stress for Method 1 is calculated from:
Sber = lesser of Sh <or> F
Allowable = (Fac)(Sber) / 1.5
Where:
Sh = Yield stress at temperature
F = Creep rupture stress at temperature
Fac = Usually 1.5, for prestressed pipe 1.35.
The Allowable Stress for Method 2 is calculated from:
Expansion Allowable = f ( 1.17S1 + 0.17S2 )
Sustained Allowable = Sh
Occasional Allowable = Sh * Occ
Where:
f = Cyclic reduction factor
S1 = lesser of Sc <or> 0.267Sy
S2 = lesser of Sh <or> 0.367Sy
Sc = Allowable stress at room temperature (Stn2)
Sh = Allowable stress at design temperature (Stn1)
Sy = Ultimate tensile strength at room temperature
Occ = Occasional Load Factor (Default=1.2)
6-100 Technical Discussions
If the weld is ground flush inside and out then the SIF of a girth butt weld can be taken to be 1.0. A weld ID = 1, informs
CAESAR II that the weld is finished and ground flush, and will result in a girth butt weld SIF of 1.0.
Swedish methods 1 and 2 Beta in the code is entered in the Pvar field on the Allowable Stress Auxiliary screen. Pvar is
entered in percent, i.e. 10.0 for ten percent. The default if no value is entered is 10 percent.
Limits on the reasonable Betas that users may enter for the Swedish piping code is 0.1 to 25%. Anything entered less than
0.1 will be taken to be 10% and anything entered greater than 25% will be taken to be 25%. If no value is entered then beta
will default to 10%. Note that 10% is entered in the Pmax field as 10.0. This applies equally for Swedish Method 1 and
Method 2.
The USE_PDo/4t line for the setup file causes the Swedish method 1 code compliance to use the thin walled equations as
given in the codes for stress calculations.
Users of Swedish Method 1 should note that implied in the CAESAR II allowable calculation is the assumption that the
SIGMA(tn) multiplier is 1.5 for piping that is not prestressed. Users of prestressed pipe (i.e. cold sprung) should change
Fac on the Allowable Stress Auxiliary field to be 1.35 as directed in the Swedish code.
Note: The corroded section modulus is used for all stress calculations as per the definition of Di in the Swedish code.
The default occasional load factor for Swedish Method 2 is 1.2.
The Swedish piping codes allow the pad thickness on an intersection to reduce stresses up to pad thickness of 2.5 times the
header wall thickness. This is greater than most codes value of 1.5 times the header wall thickness.
For reducers the Swedish piping codes states that the Flexibility Factor is 1.0. The code also states that SIF is:
2.0 max or 0.5 + .01*alpha* SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end.
Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of sloped portion of the reducer) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Chapter 6 Technical Discussions 6-101
B31.1 (1967)
The 1967 B31.1 piping code uses i
i
=i
o
for full sized intersections for both the header and the branch, and for reduced
intersections uses i
i
=0.75i
o
+ 0.25 for both the header and the branch.
Pressure stiffening is not defined by default. Users may activate pressure stiffening for B31.1 (1967) runs by entering the
parameter USE_PRESSURE_STIFFENING=YES in the setup file.
Modifications resulting from flanged ends are permitted in the code for all bends providing the bend is not a widely spaced
miter.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
No differentiation is made between socket welds with and without undercut. Codes that do differentiate use 1.3 for socket
welds with no undercut, and 2.1 for all others. An SIF of 1.3 is used for all socket welds (unless a fillet weld leg length is
specified).
B31.1 (1967) allowable stresses are computed from:
Expansion Allowable = f [ (1.25/Eff)(Sc+Sh) - Sl ]
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * Occ
Where:
f = Cyclic reduction factor
Eff = Longitudinal Weld Joint Efficiency
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Sl = Sustained Stress
Occ = Occasional Load Factor (Default=1.15)
Stoomwezen
SC = the yield stress at room temperature, referred to as Re in the code.
SH1 = the yield stress at design temperature, referred to as Re (um) in the code.
SH2 = not used
SH3 = not used
FN = the average creep stress to produce one percent set, referred to as Rrg in the code. F2
is the average creep tensile stress to produce rupture, referred to as Rmg in the code. F3 is
the minimum creep tensile stress to produce rupture, referred to as Rmmin in the code.
EFF = the cyclic reduction factor, referred to as Cf in the code.
SY = the tensile strength at room temperature, referred to as Rm in the code.
FAC = a constant whose value is either 0.44 or 0.5. Refer to Stoomwezen Section 5.2 for
details.
PVAR = the Cm coefficient in the code whose value is usually 1.0.
Stoomwezen does not make mention of reducers for SIF calculations.
6-102 Technical Discussions
RCC-M Subsection C and D
Pressure stiffening is not defined by default in the code. Users may include pressure stiffening on bends in the analysis by
including the parameter.
USE_PRESSURE_STIFFENING=YES in the configuration file.
Modifications resulting from flanged ends are permitted in the code providing the bend is not a widely spaced miter.
In-plane and out-of-plane stress intensification factors are the same for these piping codes.
Users who do not wish to use the stress intensification factor for branch connections found in Figure C3680.1 of the code
for welding and reinforced reduced tees, should set NO_REDUCED_SIF_FOR_RFT_ AND_WLT=YES in the
configuration file.
The allowables for RCC-M C and D are computed from:
Expansion Allowable = F (1.25Sc + 0.25Sh)+(Sh - SSl)
Sustained Allowable = Sh
Occasional Allowable = OCC + Sh (Defaults to 1.2, Level B)
(Use OCC = 1.8 for Level C)
(Use OCC = 2.4 for Level D)
Where:
F = Cyclic reduction factor
Sc = Cold allowable
Sh = Hot allowable
S
sl
= Sustained stress (PD/4t + 0.75i M
b
/Z)
OCC = Occasional factor from the CAESAR II configuration file)
The Pvar value in the allowable stress spreadsheet is for the DIFFERENCE between the design pressure and Pmax to be
used in equation 10.
Equations 7 or 8 are satisfied by using as the allowable for the i M
c
/Z stress the maximum of either F (1.25Sc + 0.25Sh) or F
(1.25Sc + 0.25Sh) + (Sh - S
sl
) where S
sl
is the sustained stress as defined by equation 6. For reducers RCC-M states that the
Flexibility Factor is 1.0. The code also states that SIF is:
2.0 max or 0.5 + .01*alpha* SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end. Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of sloped portion of reducer) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Note: Alpha cannot exceed 60 and the larger of D1/t1 and D2/t2 cannot exceed 100.
Chapter 6 Technical Discussions 6-103
CODETI
Modifications resulting from flanged ends are permitted in the code for all bends, including widely spaced miters.
Inplane and outplane stress intensification factors of intersections are kept separate and unique.
Since CODETI gives the equation for the expansion stress explicitly, and since that equation does not include the
longitudinal stress due to axial loads in the pipe, CAESAR II does not include the F/A component of the stress in the
expansion stress equation. Users can change this by setting ADD_F/A_IN_STRESS=YES to the configuration file. The F/A
longitudinal stress component are by default added to the code stress component for all other stress categories.
Stress allowables for CODETI are calculated from
Expansion Allowable = F [1.25 (Sc + Sh)] - Sl
Sustained Allowable = Sh
Occasional Allowable = OCC x Sh
Where:
F = Cyclic reduction factor
Sc = Cold allowable stress
Sh = Hot allowable stress
Sl = Sustained stress
OCC = Occasional load factor from configuration (defaults to 1.15)
Pressure stiffening of bends is automatically included as directed by the code. Users may deactivate it by setting the
parameter USE_PRESSURE_STIFFENING=NO in the configuration file.
Flexibility coefficients and stress intensification factors are phased in for bends with an included angle between 15 and 45.
Their value is 1.0 for smaller than 15 bends.
The stress intensification factor of fabricated tees having an angle of incidence other than 90 are increased by dividing
them by (sin a)
3/2
.
Recommended occasional load factors are 1.15, 1.2, and 1.3, as per Code Table C3.3.
CODETI requires that when the design temperature is such that the creep characteristics are determinant, and if a section of
the piping presents locally weaker characteristics, the sum of the primary and secondary stresses must not exceed the value
F
F
(from Section C1.4.3). This requirement has not been implemented in CAESAR II and has been left to the user to verify.
For reducers CODETI states that the Flexibility Factor is 1.0 and the SIF is 1.0.
Norwegian (TBK 5-6)
Pressure stiffening of bends is required for flexibility factors only and is done that way, by default. Users may deactivate
pressure stiffening completely by setting USE_PRESSURE_STIFFENING=NO in the configuration file. Pressure stiffening
may be activated for stress intensification factors as well by setting USE_PRESSURE_-STIFFENING=YES.
The Norwegian Code does not by default add F/A into the stress calculation. The user can cause CAESAR II to include the
axial force term into the code stress by setting ADD_F/A_IN_STRESS=YES in the configuration file.
The code uses a circumferential weld strength factor (Z) when calculating longitudinal pressure stress. This value is entered
as EFF.
6-104 Technical Discussions
The cyclic reduction factor should be calculated as F = (7000/Ne)
0.2
(where Ne is the number of anticipated cycles), and
may be as high as 2.34, but shall not be greater than 1.0 when Rm governs the expansion stress allowable.
In-plane and out-of-plane stress intensification factors for bends and intersections are kept the same in the stress calculation.
Stress allowables for the Norwegian Code are
Expansion allowable = Sr + F2 - SSUS
Sustained allowable = F2
Occasional allowable = Occ x F2
Where:
Sr = Minimum of 1.25F
1
+ 0.25F
2
; Fr x Rs - F
2
; or Fr (1.25 R
1
+ 0.25 R
2
) (The latter for higher
temperatures; above 425C for austenitic stainless steel, or above 370C for other materials)
F
2
= Hot allowable stress (entered in Sh)
OCC = Occasional load factor from the configuration file (defaults to 1.2)
S
SUS
= Sustained stress
F
1
= Allowable stress at ambient (entered in Sc)
Fr = Cyclic reduction factor
Rs = Permissible extent of stress for 7000 cycles (from Code Table 10.2)
R
1
= Smaller of F
1
and 0.267 R
M
R
2
= Smaller of F
2
and 0.367 R
M
Rm = Ultimate tensile strength at room temperature
Stress intensification factors for fitting types 6 (branch with raised edge radius), 7 (branch on locally thickened pipe), 13
(conical reducer with knuckles), and 14 (reducer without knuckles) have not been implemented in CAESAR II and are the
responsibility of the user to enter manually.
The Norwegian code offers an alternative stress analysis method in Appendix D. CAESAR II does not implement that
method.
For reducers the Norwegian code states that the Flexibility Factor is 1.0. The code also states that SIF is: 2.0 max or 0.5 +
.01*alpha* SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end.
FDBR
FDBR is similar to B31.1 in most aspects. However, the following differences should be noted.
For reinforced tees, FDBR limits the pad thickness to a maximum equal to the header thickness. If a pad thickness greater
than the header thickness is entered, the program overrides it with the header thickness.
Reduced intersections are treated as in ASME NC, not as in B31.1.
The SIF values for butt welds differ from B31.1. FDBR uses either 1.0 or 1.8, depending on the thickness.
FDBR requires the use of the Hot Modulus of Elasticity in the flexibility analysis. Additionally, the computation of the
Expansion Case Allowable Stress incorporates the ratio of Ehot to Ecold. The user can override the program computed ratio
by manually entering it in the FAC field.
Chapter 6 Technical Discussions 6-105
For reducers FDBR states that the Flexibility Factor is 1.0. The code also states that SIF is:
2.0 max or 0.5 + .01*alpha* SQRT(D2/t2)
Where D1 and t1 are the diameter and thickness of the large end and D2 and t2 are the diameter and thickness of the small
end. Alpha is the reducer cone angle in degrees.
Where:
Alpha = atan[ 0.5 * (D1-D2) / (0.60 * length of sloped portion of reducer*) ]
Tip: Alpha is the slope of the reducer transition in degrees. If left blank, the value will be set from an
estimated slope equal to the arc tangent times 1/2 the change in diameters times sixty percent of the
entered reducer length.
Note: Alpha cannot exceed 60 and the larger of D1/t1 and D2/t2 cannot exceed 100.
BS 7159
BS 7159 for Fiberglass Reinforced Plastic (FRP) Pipe requires that a single load case (OPE) be evaluated. For that case, the
following combined stress requirements must be met:
If Sx is tensile:
( )
( )
2 2
P D [sqrt((i M ) +(i M ) )]
m xi i xo o
S = +
x
4t Z
2 2
4S
x s
Sh o + <
(OPE)
and
2 2
( 4 ) *
s
o + o <
|
Sh E E
H A
(OPE)
or, if Sx is compressive:
( )
( )
2 2
P D [sqrt((i M ) +(i M ) )]
F m xi i xo o x
- -
A
4t Z
(If Fx/A > P(Dm)/(4t), and it is compressive)
(OPE)
and
(OPE)
Circumferential Stress
( )
( )
MP D
m
S =
2t
|
for straight pipes
( )
( )
2 2
[ ((i M ) +(i M ) ) ]
MP D i i o o
m
+
2t Z
| |
=
for bends
6-106 Technical Discussions
( )
( )
2 2
[ ((i M ) +(i M ) ) ] MP D
i i o o m
+
2t Z
x x
=
for tees
Dm and t are always for the Run Pipe
BS 7159 allowables are based on material design strain e
d
. Therefore allowable stresses differ in the axial and hoop
directions by the ratio of the axial and hoop moduli of elasticity:
S
h
= c
d
E
x
S
HOOP
= (c
d
E
x
) (E
h
/E
x
)
The ratio E
h
/E
x
is entered in the allowable stress Eff field; if omitted, it defaults to 1.0 (isotropic material).
Pressure stiffening of bends is done assuming the bends are fully pressurized up to the design strain of the components (as
per the code requirements). This can be deactivated by setting USE_PRESSURE_STIFFENING = NO in the configuration
file.
BS 7159 does not by default add F/A into the stress calculation (unless this puts an element into compression as described
above). The user can cause CAESAR II to include the axial force term into the code stress by setting ADD_F/A_IN_STRESS
= YES in the configuration file.
The fatigue factor K
n
is used inversely relative to the cyclic reduction factor in most codes, so its value should be greater
than or equal to 1.0 (allowable stress is divided by this number). K
n
is calculated as:
K
n
= 1.0 + 0.25 (A
s
/o
n
) (Log
10
(n) - 3.0)
Where:
A
s
= stress range during fatigue cycle
o
n
= maximum stress during fatigue cycle
n = number of cycles during design life
K
n
is entered in the Cyclic Reduction Factor field(s).
BS 7159 requires that the temperature of the pipe material be considered as being typically only 80% - 85% of the
difference between the fluid and the ambient temperatures. This reduction factor K is entered in the allowable stress FAC
field; if omitted, it defaults to 1.0.
The stress intensity and flexibility factors of bends vary based on laminate type:
All chopped strand mat (CSM) construction with internal and external surface tissue reinforced layer
Chopped strand mat (CSM) and woven roving (WR) construction with internal and external surface tissue reinforced
layer
Chopped strand mat (CSM) and multi-filament roving construction with internal and external surface tissue reinforced
layer
The laminate type may be entered in the Bend Type field, or a type default may be set in the Special Execution Parameter
screen.
BS 7159 does not make mention of reducers for SIF calculations.
UKOOA
The UKOOA (United Kingdom Offshore Operators Association) Specification and Recommended Practice for the Use of
GRP Piping Offshore is similar in many respects to the BS 7159 Code, except that it simplifies the calculational
requirements in exchange for imposing more conservatism on the piping operating conditions. Rather than explicitly
calculating a combined stress, the specification defines an idealized envelope of combinations of axial and hoop stresses
which cause the equivalent stress to reach failure. This curve represents the plot of:
Chapter 6 Technical Discussions 6-107
(o
x
/ o
-all
)
2
+ o
hoop
/ o
hoop-all
)
2
- [o
x
o
hoop
/ (o
x-all
o
hoop-all
)] s 1.0
Where:
o
x-all
= allowable stress, axial
o
hoop-all
= allowable stress, hoop
The Specification conservatively limits the user to that part of the curve falling under the line between s
x-all
(also known as
s
a(0:1)
) and the intersection point on the curve where s
hoop
is twice s
x
-(a natural condition for a pipe loaded only with
pressure). An implicit modification to this requirement is the fact that pressure stresses are given a factor of safety (typically
equal to 2/3) while other stresses are not. This gives an explicit requirement of:
P
des
s f
1
f
2
f
3
LTHP
Where:
P
des
= allowable design pressure
f
1
= factor of safety for 97.5% lower confidence limit, usually 0.85
f
2
= system factor of safety, usually 0.67
f
3
= ratio of residual allowable, after mechanical loads
= 1 - (2 s
a
b
) / (r f
1
LTHS)
o
a
b
= axial bending stress due to mechanical loads
r = s
a(0:1)
/ s
a(2:1)
o
a(0:1)
= long term axial tensile strength in absence of pressure load
o
a(2:1)
= long term axial tensile strength in under only pressure loading
LTHS = long term hydrostatic strength (hoop stress allowable)
LTHP = long term hydrostatic pressure allowable
Note: This has been implemented in the CAESAR II pipe stress analysis software as:
Code Stress Code Allowable
o
a
b
(f
2
/r) + PD
m
/ (4t) s (f
1
f
2
LTHS) / 2.0
Where:
P = design pressure
D
m
= pipe mean diameter
t = pipe wall thickness
On the Allowable auxiliary screen, the product of f
1
and LTHS is entered in the SH1, SH2, SH3 fields; r is entered in the
F1, F2, F3 fields; f
2
is entered in the EFF field; and the temperature reduction factor K (described for BS 7159 above) is
entered in the FAC field if omitted, it defaults to 1.0. K- and i-factors for bends and tees, and bending and pressure
stresses are calculated as described for the BS 7159 Code.
Note: UKOOA refers to BS7159 for SIF calculations.
6-108 Technical Discussions
IGE/TD/12
CAESAR II performs calculations as per the IGE/TD/12 Edition 2 code requirements. The complexity of these requirements
far exceeds what can be described here. It is recommended that the user acquire a copy of this code from the International
Institution of Gas Engineers & Managers or request COADEs supplementary IGE/TD/12 documentation.
Note: The current implementation of IGE/TD/12 has not been granted approval for use on Transco projects.
Det Norske Veritas (DNV)
This code is entitled Rules for Submarine Pipeline Systems. The Allowable Stress Design (ASD) provisions of the code
are implemented here, rather than the limit state requirements.
Since DNV does not provide any guidance on Stress Intensification Factors, Flexibility Factors, or section moduli; these are
calculated as per the B31.1 Power Code (this decision was based upon an informal poll of experts and users of DNV). All
stress calculations are made using the corroded wall thickness.
Operating, Sustained, or Occasional load cases are treated identically (there is no provision for a code check for an
Expansion load case, so no Expansion cases are generated under this code). For these load cases, three stress calculations
are done, with different allowables. The stress calculation causing the highest percent of allowable is reported in the stress
report, along with its specific allowable. These stress checks are:
Hoop Stress: S
h
s n
s
SMYS
Hoop Stress: S
h
s n
u
SMTS
Longitudinal Stress: S
L
s n SMYS
Equivalent Stress: S
e
s n SMYS
Where:
S
h
= (P
i
P
e
) (D t) / 2t
P
i
= internal pressure
P
e
= external pressure
D = outer diameter
t = wall thickness
n
s
= hoop stress yielding usage factor (see Tables C1 and C2 of the DNV Code)
SMYS = specified minimum yield strength, at operating temperature
n
u
= hoop stress bursting usage factor (see Tables C1 and C2 of the DNV Code)
SMTS = specified minimum tensile strength, at operating temperature
S
L
= maximum longitudinal stress
n = equivalent stress usage factor (see Table C4 of the DNV Code)
S
e
= [S
h
2
+ S
L
2
- S
h
S
L
+ 3t
2
]
1/2
t = torsional stress
DNV does not make mention of reducers for SIF calculations.
Chapter 6 Technical Discussions 6-109
EN-13480
EN-13480 uses the hot modulus of elasticity in the flexibility calculations (Sect 12.1.7.2). The expansion allowable stress
is subsequently modified by the ratio of Eh/Ec.
EN-13480 provides two methods of determining the flexibility stresses. The CAESAR II default implementation is to use
Sections 12.3.2 through 12.3.6, which perform an SRSS of the bending moments with a single SIF. As an alternative, the
flexibility stresses can be determined by distinguishing between in and out of plane bending, using distinct SIFs, as
discussed in Section 12.3.1. The option to implement this alternative can be found on the "SIF & Stress" tab of the
configuration module.
EN-13480 does not consider pressure stiffening effects on bends.
GPTC/Z380
GPTC/Z380 is basically the B31.8 piping code, prior to the 2004 edition of B31.8. The recommendations of this code only
apply to steel piping, above ground, up through 450F. The differences between GPTC/Z380 and B31.8 display below:
The longitudinal joint factors vary slightly between B31.8 Table 841.115a and GPTC/Z380 Table 192.113.
The design factor in B31.8 Table 841.114b is more detailed than GPTC/Z380 Table 192.11.
The allowable for the combined stress calculation in GPTC/Z380 Section 192.159-1.5e includes a "0.75" factor, while
B31.8 Section 833.4 does not.
GPTC/Z380 uses a single SIF for both in and out of plane loads, while B31.8 distinguishes between in and out of plane
SIFs.
ISO-14692
ISO-14692 addresses the analysis of Fiber Reinforced Piping (FRP). Qualification is based on the comparison of actual
stresses (hoop and axial) to a failure envelope there is no single allowable stress value. For the proper implementation of
this code several FRP specific quantities MUST BE defined, as shown in the figure below.
For details on the input fields in the figure above, please consult the Online Help.
6-110 Technical Discussions
HPGSL
Inplane and outplane stress intensification factors for intersections are kept separate and unique.
Since the HPGSL piping code gives the equation for the expansion stress explicitly, and since that equation does not include
the longitudinal stress due to axial loads in the pipe, CAESAR II does not include the F/A component of the stress in the
expansion stress equation. The F/A longitudinal stress component are by default added to the code stress component for all
other stress categories.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
No differentiation is made between socket welds with and without undercut. Codes that do differentiate use 1.3 for socket
welds with no undercut, and 2.1 for all others. An SIF of 1.3 is used for all HPGSL socket welds (unless a fillet weld leg
length is specified).
Stress allowables for HPGSL are calculated from:
Expansion Allowable = f [ (1.25/Eff)(Sc+Sh) - Sl ]
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * (Occ)
Where:
f = Cyclic reduction factor
Eff = Weld Joint Efficiency (Only for minimum wall thickness)
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Sl = Sustained Stress
Occ= Occasional Load Factor (Default = 1.33)
For HPGSL if a corrosion allowance is specified, the corrosion is removed from the sustained and occasional stress
calculations.
Pressure effects on miters are allowed in the HPGSL piping code.
For reducers HPGSL states that the Flexibility Factor is 1.0. The code also states that SIF is 1.0.
JPI
Inplane and outplane stress intensification factors for intersections are kept separate and unique.
Since JPI gives the equation for the expansion stress explicitly, and since that equation does not include the longitudinal
stress due to axial loads in the pipe, CAESAR II does not include the F/A component of the stress in the expansion stress
equation. The F/A longitudinal stress component are by default added to the code stress component for all other stress
categories.
The SIF for a girth butt weld is taken as 1.0, as this was Markls original basis for SIFs.
No differentiation is made between socket welds with and without undercut. Codes that do differentiate use 1.3 for socket
welds with no undercut, and 2.1 for all others. An SIF of 1.3 is used for all HPGSL socket welds (unless a fillet weld leg
length is specified).
Chapter 6 Technical Discussions 6-111
Stress allowables for HPGSL are calculated from:
Expansion Allowable = f [ (1.25/Eff)(Sc+Sh) - Sl ]
Sustained Allowable = Sh/Eff
Occasional Allowable = Sh/Eff * (Occ)
Where:
f = Cyclic reduction factor
Eff = Weld Joint Efficiency (Only for minimum wall thickness)
Sc = Cold Allowable Stress
Sh = Hot Allowable Stress
Sl = Sustained Stress
Occ = Occasional Load Factor (Default = 1.33)
For JPI if a corrosion allowance is specified, the corrosion is removed from the sustained and occasional stress calculations.
Pressure effects on miters are allowed in piping code HPGSL.
For reducers JPI states that the Flexibility Factor is 1.0. The code also states that SIF is 1.0.
6-112 Technical Discussions
Local Coordinates
Many analytical models in engineering are based upon being able to define a real physical object mathematically. This is
accomplished by mapping the dimensions of the physical object into a similar mathematical space. Mathematical space is
usually assumed to be either two-dimensional or three-dimensional. For piping analysis, the three dimensional space is
necessary, since almost all piping systems are three dimensional in nature.
Two typical three-dimensional mathematical systems are shown below in Figure 1. Both of these systems are Cartesian
Coordinate Systems. Each axis in these systems is perpendicular to all other axes.
Figure 1 Typical Cartesian Coordinate Systems
In addition, for these Cartesian coordinate systems, the right hand rule is used to define positive rotation about each axis,
and the relationship, or ordering, between the axes. Before illustrating the right hand rule, there are several traits of the
systems in Figure 1 that should be noted.
Each axis can be thought of as a number line, where the zero point is the point where all of the axes intersect.
While only the positive side of each axis is shown in Figure 1, each axis has a negative side as well.
The direction of the arrow heads indicates the positive direction of each axis.
In Figure 1, the X axis has one arrowhead, the Y axis has two arrowheads, and the Z axis has three arrowheads.
The circular arcs labeled RX, RY, and RZ define the direction of positive rotation about each axis. (This point
will be discussed later.)
Any point in space can be mapped to these coordinate systems by using its position along the number lines. For
example, a point 5 units down the X axis would have a coordinate of (5.0, 0.0, 0.0). A point 5 units down the X
axis and 6 units down the Y axis would have a coordinate of (5.0, 6.0, 0.0).
Notice that if the system on the right side of Figure 1 is rotated a positive 90 degrees about the X axis, the result is the
system on the left side of Figure 1.
The coordinate system on the left side of Figure 1 is the default CAESAR II global coordinate system. In this system, the X
and Z axes define the horizontal plane, and the Y axis is vertical. (The other coordinate system in Figure 1 can be
obtained in CAESAR II by selecting the Z-axis Vertical option, discussed later in this chapter.) All further discussion in
this chapter will target this default coordinate system, unless otherwise noted.
Chapter 6 Technical Discussions 6-113
Other Global Coordinate Systems
There are other types of coordinate systems that can be used to mathematically map a physical object.
A Polar coordinate system maps points (in a two dimensional space) using a radius and a rotation angle, (r, theta).
A Cylindrical coordinate system maps points using a radius, a rotation angle, and an elevation, (r, theta, z). The
origin in this system could be considered the center of the bottom of a cylinder. Cylindrical coordinates are convenient
to use when there is an axis of symmetry in the model.
A Spherical coordinate system maps points using a radius and two rotation angles, (r, theta, phi). The origin in this
system could be considered the center of a sphere. Spherical coordinates are convenient to use when there is a point
which is the center of symmetry in the model.
Typically, none of these coordinate systems are easily used to map piping systems. Most piping software deals exclusively
with the Cartesian coordinate system.
The Right Hand Rule
In the Cartesian coordinate system, each axis has a positive and a negative side, as previously mentioned. Translations,
straight-line movement, can be defined as movement along these axes. Rotation can also occur around these axes, as
illustrated by the arcs in Figure 1.
A standard rule must be applied in order to define the direction of positive rotation about these axes. This standard rule
(known as the right hand rule) is: Put the thumb of your right hand along the axis, in the positive direction of the axis.
The direction your fingers curl is positive rotation about that axis. This is best illustrated in Figure 2.
Figure 2 The Right Hand Rule
The right hand rule can also be used to describe the relationship between the three axes. Mathematically, the relationship
between the axes can be defined as:
X cross Y = Z EQ 1
Y cross Z = X EQ 2
Z cross X = Y EQ 3
Where cross indicates the vector cross product.
6-114 Technical Discussions
Physically, using your right hand, what do the above equations mean? This question is best answered by Figure 3.
Figure 3 The Right Hand Rule - Continued
The left pane of Figure 3, corresponds to vector equation 3 above. Similarly, the center pane in Figure 3 also corresponds to
vector equation 3 above. The right pane in Figure 3 corresponds to vector equation 2 above. All panes of Figure 3 refer to
the left hand image of Figure 1.
Straight-line movement along any axis can be therefore described as positive or negative, depending on the direction of
motion. This straight-line movement accounts for three of the six degrees of freedom associated with a given node point in
a model. (Analysis of a model requires the discretization of the model into a set of nodes and elements. Depending on the
analysis and the element used, the associated nodes have certain degrees of freedom. For pipe stress analysis, using 3D
Beam Elements, each node in the model has six degrees of freedom.) The other three degrees of freedom are the rotations
about each of the axes. In accordance with the right hand rule, positive rotation about each axis is defined as shown in
Figures 1 and 2.
When modeling a system mathematically, there are two coordinate systems to deal with, a global (or model) coordinate
system and a local (or elemental) coordinate system. The global or model coordinate system is fixed, and can be considered
a constant characteristic of the analysis at hand. The local coordinate system is defined on an elemental basis. Each
element defines its own local coordinate system. The orientation of these local systems varies with the orientation of the
elements.
Note: An important concept here (which will be reiterated later) is the fact that local coordinate systems are defined by,
and therefore associated with, elements. Local coordinate systems are not defined for, or associated with, nodes.
Chapter 6 Technical Discussions 6-115
Pipe Stress Analysis Coordinate Systems
As noted previously, most pipe stress analysis computer programs utilize the 3D Beam Element. This element can be
described as an infinitely thin stick, spanning between two nodes. Each of these nodes has six degrees of freedom - three
translations and three rotations. Piping systems (models) are constructed by defining a series of elements, connected by
nodes. These pipe elements are typically defined as vectors, in terms of delta dimensions referenced to a global
coordinate system. Several example pipe elements are shown below in Figure 4.
Figure 4 - Example Pipe Elements
For most pipe stress applications, there are two dominant global coordinate systems to choose from, either Y axis or Z
axis up. These two systems are depicted in Figure 1. As previously noted, the global coordinate system is fixed. All nodal
coordinates and element delta dimensions are referenced to this global coordinate system. For example, in Figure 4 above,
the pipe element spanning from node 10 to node 20 is defined with a DX (delta X) dimension of 5 ft. Additionally, node 20
has a global X coordinate 5 ft. greater that the global X coordinate of node 10. Similar statements could be made about
the other two elements in Figure 4, only these elements are aligned with the global Y and global Z axes.
In CAESAR II, the user can choose between the two global coordinate systems shown in Figure 1. By default, the CAESAR II
global coordinate system puts the global Y axis vertical, as shown in the left half of Figure 1, and in Figure 4. There are
two ways to change the CAESAR II global coordinate system so that the global Z axis is vertical.
The first method is to modify the configuration file in the current data directory. This can be accomplished from the Main
Menu, by selecting TOOLS\CONFIGURE SETUP. Once the configuration dialog appears, select the Geometry tab, as shown in
Figure 5. On this tab, check the Z Axis Up check box, as shown in the figure below.
6-116 Technical Discussions
Figure 5 - Geometry Configuration
Once the Z Axis Vertical check box is activated, the CAESAR II global coordinate system will be in accordance with the
right half of Figure 1. This configuration affects all new jobs created in this data directory. Existing jobs with the Y axis
vertical are not affected by this configuration change.
The second method to obtain a global coordinate system with the Z axis vertical is to switch coordinate systems from
within the input for the specific job at hand. This can be accomplished from the Special Execution Parameters dialog of
the piping input processor. This dialog is shown below in Figure 6.
Chapter 6 Technical Discussions 6-117
Figure 6 - Special Execution Parameters Dialog
Checking the Z Axis Vertical check box will immediately change the orientation of the global coordinate system axis, with
corresponding updates to the element delta dimensions. However, the relative positions and lengths of the elements are not
affected by this switch.
6-118 Technical Discussions
Defining a Model
Using the CAESAR II default coordinate system (Y axis vertical), and assuming the system shown below in Figure 7, the
corresponding element definitions are given in Figure 8.
Figure 7 - Sample Piping Model
Figure 8 - Sample Piping Model Element Definitions
For this sample model, most of the element definitions are very simple:
The first element, 10-20, is defined as 5 ft. in the positive global X direction. This element starts at the model origin.
The second element, 20-30, is defined as 5 ft. in the positive global Y direction. This element begins at the end of the
first element, since both elements share node 20.
The third element, 30-40, is defined as 5 ft. in the negative global Z direction. Note in Figure 8 that the delta
dimension for this element is a negative number. This is necessary to define the element in a negative direction.
The fourth element, 40-50, runs in both the positive global X and negative global Y directions, this element slopes
to the right and down. This element is defined with delta dimensions in both the DX and DY fields. Notice that these
delta dimensions are equal in magnitude; therefore this element slopes at 45 degrees.
Chapter 6 Technical Discussions 6-119
Continuing the model, from node 50, along the same 45 degree slope can be rather tedious, since most often only the
overall element length is know, not its components in the global directions. In CAESAR II this can be best accomplished
by activating the Direction Cosine dialog box, shown below in Figure 9. The Direction Cosine dialog can be activated
by clicking the Browse button next to the DY field. Using this dialog box, the element length can be entered, and
CAESAR II will determine the appropriate components in the global directions, based on the current direction cosines
(which default to those of the preceding element).
Figure 9 - Direction Cosine Dialog
CAESAR II provides an additional coding tool, for longer runs of pipe with uniform node spacing. An element break
option is provided, which allows an element to be broken into equal length segments, given a node number increment.
In the preceding example, the model is defined solely using delta dimensions. By constructing the model in this fashion,
it is assumed that the world coordinates of node 10 (the first node in the model) are at (0., 0., 0.). This assumption is
acceptable in all but a one instance, when environmental loads are applied to the model. In this instance, the elevation of
the model is critical to the determination of the environmental loads, and therefore must be specified. In CAESAR II, the
specification of the starting node of the model can be accomplished using the [Alt+G] key combination, and all nodal
coordinates will be displayed as absolute coordinates. Regardless of whether or not the global coordinates of the starting
node are specified, the model relative geometry will plot the same.
Once a model has been defined, there are a number of operations that can be performed on the entire system, or on any
section of the system. These operations include:
Translating the model: translation can be accomplished by specifying the global coordinates of the starting node of the
model. If the model consists of disconnected segments, CAESAR II requests the coordinates of the starting node of each
segment.
6-120 Technical Discussions
Rotating the model: rotation can be accomplished by using the [LIST] processor or by clicking the button. The
[LIST] processor presents the model in a spreadsheet, or grid, format, as shown in Figure 8. Options in this processor
allow the model (or any sub-section of the model) to be rotated about any of the three global axes, a specified amount.
For example, if the model shown in Figures 7 and 8 is rotated a (negative) -90 degrees about the global Y axis, the
result is as shown in Figure 10.
Figure 10 - Example of Model Rotation
Duplicating the model: duplication can also be accomplished by using the [LIST] processor. The entire model, or any
sub-section of the model, can be duplicated.
Using Local Coordinates
When analyzing a piping system, there are a number of items that must be checked and verified. These items include:
Operating Loads On Restraints & Terminal Points Maximum Operating Displacements
Hanger design results Code stresses for code cases
Equipment Evaluations Vessel Nozzle Evaluation
Expansion joint evaluation
Restraint loads and displacements are checked in the global coordinate system. This is necessary because restraint loads
and displacements are nodal quantities. Element loads and stresses are most often evaluated in their local coordinate
system. A good example illustrating the use of a local (element) coordinate system is the free body diagram, of forces and
moments. The forces and moments in this free body diagram remain the same, regardless of the position of the element in
the global coordinate system. Note however, that each element has its own local coordinate system. Furthermore, the local
coordinate system of one element may be different from the local coordinate system of a different element.
While the global coordinate system is typically referred to using the capital letters X, Y, and Z, local coordinate
systems use a variety of nomenclature. In almost all cases, local coordinate systems use lower case letters. Typical local
coordinate system axes are: xyz, abc, and uvw. CAESAR II uses xyz to denote the local element coordinate system.
The local coordinate system for an element is related to the global coordinate system through a rule. There may be a
number of such rules, depending on the type of element. In CAESAR II, the following rules are used to define the local
coordinate systems of the piping elements in a model.
Chapter 6 Technical Discussions 6-121
CAESAR II Local Coordinate Definitions
Rule 1 - Straight Pipe: For straight pipe elements, the local x axis always points from the FROM node to the To
Node. The local y axis can be found by the vector cross product of the local x axis with the global Y axis. Applying
the right hand rule, this local y axis can be found by performing the following steps:
1 Lay your right hand on the pipe, with the wrist at the FROM node, and the fingers pointing to the To Node.
2 Align or rotate your hand so that the global Y axis points perpendicularly out from the palm. The thumb is now
aligned with the local y axis for this element.
The local z axis can be found by the vector cross product of the local x and local y axes.
An exception to this rule is the case of a vertical element. In this case, the local x axis is still aligned in the From - To
direction. However, you cant cross a vertical element into global Y, so the local y axis was arbitrarily assigned to
align with the global X axis.
The straight elements of the model in Figure 7 are reproduced below in Figure 11, along with their local coordinate systems.
Notice that each of these straight elements has its own local coordinate system, and that in this model, they are all aligned
differently.
Figure 11 - Local Coordinate Systems for Straight Elements (1)
In Figure 11, the positive direction of the local x axis for each element is defined according to the From - To definition
of the element. For example, the local x axis of element 10-20 is aligned with the positive global X axis, because that is
the direction defined in moving from node 10 to node 20. The local x axis of element 30-40 is aligned with the negative
global Z axis, because that is the direction defined in moving from node 30 to node 40. Figure 11 should be studied to
ensure a good understanding of how the local element coordinate system can be defined based on the definition of the
element, especially with regard to the skewed element 40-50.
As an additional example, the local element coordinate systems for the rotated system of Figure 10 are shown below in
Figure 12.
6-122 Technical Discussions
Figure 12 - Local Coordinate Systems for Straight Elements (2)
Rule 2 - Bend Elements: For the near weld line of bend elements, the local x axis is directed along the incoming
tangent, in the From To direction. The local z axis points to the center of the circle described by the bend. For the
far weld line of bend elements, the local x axis is directed along the outgoing tangent, in the From To direction.
The local z axis points to the center of the circle described by the bend. In both cases, the local y axis can be found by
applying the right hand rule. The local coordinate system for the bends in the example model of Figure 7 display below
in Figure 13.
Figure 13 Local Coordinate Systems for Bend Elements
Rule 3 - Tee Elements: For tees, there is no element or fitting as there is in a CAD application. Rather designating a
node as a tee simply applies code defined SIFs at that point, for the three elements framing into the tee node. As usual, the
local xaxis is defined by the element From - To direction. The local y axis coincides with the line that defines the
in-plane plane of the tee (in other words, the local y axis is perpendicular to the plane of the three tee elements). The
positive direction of the local y axis is found by (vectorally) crossing the local x axis of the header element with the
local x axis of the branch, and then (strangely enough) reversing the sign (direction). (In those cases where the two
Chapter 6 Technical Discussions 6-123
header elements have opposite local x axes, CAESAR II chooses the first one that it finds.) The local z axis can then be
determined using the right-hand rule.
Note that the local z axis coincides with the out-of-plane axis of the tee, for each element. Examples of local
coordinates for elements framing into tees are depicted below in Figure 14.
Figure 14 - Local Coordinate Systems for Tee Elements
Applications - Utilizing Global and Local Coordinates
Global coordinates are used most often when dealing with piping models. Global coordinates are used to define the model
and review nodal results. Even though element stresses are defined in terms of axial and bending directions, which are
local coordinate system terms, local coordinates are rarely used. A typical piping analysis scenario is as follows.
A decision is made as to how the global coordinate system for the piping model will align with the plant coordinate
system. Usually, one of the two horizontal axes is selected to correspond to the North direction. However, if this
results in a majority of the system being skewed with respect to the global axes, one should consider realigning the
model. It is best to have most of the system aligned with one of the global coordinate axes.
The piping system is then assigned node points at locations where: there is a change in direction, a support, a terminal
point, a point of cross section change, a point of load application, or any other point of interest.
Once the nodes have been assigned the piping model can be defined using the delta dimensions as dictated by the
orientation of the global coordinate system. Analysts should take advantage of the tools provided by CAESAR II in
constructing the model - this includes the element Break option, the LIST, Rotate and Duplicate options, and the
Direction Cosine facility.
After verifying the input, confirming the load cases, and analyzing the model, output review commences.
Output review involves checking various output reports to ensure the system responds within certain limits. These checks
include:
6-124 Technical Discussions
Checking that operating displacements make sense and are within any operational limits (to avoid ponding etc.).
Displacements being nodal quantities, are reviewed in the global coordinate system. There is no local coordinate
system associated with nodes. For the model defined in Figures 7 and 8, the operating displacements are shown in
Figure 15 below.
Figure 15 - Operating Displacements
This report shows the movements of all of the nodes in the model, in each of the six degrees of freedom, in the global
coordinate system.
Chapter 6 Technical Discussions 6-125
Checking that the restraint loads for the structural load cases are reasonable. This includes ensuring that the
restraints can be designed to carry the computed load. Restraints being nodal quantities are reviewed in the global
coordinate system. There is no local coordinate system associated with restraints. For the model defined in Figures
7 and 8, the operating / sustained restraint summary is shown in Figure 16 below.
Figure 16 - Operating / Sustained Restraint Summary
This report shows the loads on the anchor at 10 and the nozzle at 50, for all six degrees of freedom, for the two selected
structural load cases, in the global coordinate system.
6-126 Technical Discussions
Checking the Code cases for codes stress compliance. Typically the code stress is compared to the allowable
stress for each node on each element. Occasionally, when there is an overstress condition, a review of axial, bending,
and torsion stresses are necessary. These stresses (axial, bending, and torsion) are local coordinate system terms, and
therefore relate to the elements local coordinate system. For the model defined in Figures 7 and 8, a portion of the
sustained stress report is shown in Figure 17 below.
Figure 17 - Sustained Stress Report
These reports provide sufficient information to evaluate the pipe elements in the model, to ensure proper behavior and code
compliance. However, the analysts job is not complete, loads and stress must still be evaluated at terminal points, where
the piping system connects to equipment or vessel nozzles. Depending on the type of equipment or nozzle, various
procedures and codes are applied. These include API-610 for pumps and WRC-107 for vessel nozzles, as well as others. In
the case of API-610 and WRC-107, a local coordinate system specific to these codes is employed. These local coordinate
systems are defined in terms of the pump or nozzle/vessel geometry.
When the equipment coordinate system aligns with the global coordinate system of the piping model, the nozzle loads from
the restraint report (node 50 in Figure 14) can be used in the nozzle evaluation. However, when the equipment nozzle is
skewed (as it is in the case of node 50 in Figure 14), the application of the loads is more difficult. In this case, it is best to
use the loads from the elements force/moment report, in local coordinates. The only thing to remember here is to flip the
signs on all of the forces and moments, since the element force/moment report shows the loads on the pipe element, not on
the nozzle. For the element FROM node 40 to node 50, the local element force/moment report is shown in Figure 18
below.
Chapter 6 Technical Discussions 6-127
Figure 18 - Local Element Force/Moment Report
Because the correlation between the pipe models coordinate systems and those of equipment codes (API, WRC, etc.) are
often times tedious and error prone, CAESAR II provides an option in its equipment modules to acquire the loads on the
nozzle directly from the static output. The user simply has to select the node and the load case; CAESAR II will acquire the
loads and rotate them into the proper coordinate system as defined by the applicable equipment code. The user really does
not have to be concerned with the transformation from global to local coordinates, even for skewed components. This is
illustrated below, in Figure 19. In this figure, the API-610 nozzle loads at node 50 have been acquired by clicking the Get
Loads from Output File button.
Notice that the loads shown in Figure 19 are in the CAESAR II global coordinate system. This can be easily verified by
comparing these values to those in the restraint summary (for the Operating load case) as shown previously in Figure 16.
6-128 Technical Discussions
Figure 19 - API-610 Nozzle Load Acquisition
In the corresponding output report for this API-610 analysis, both the global and API local loads are reported. This is
shown below in Figure 20.
Figure 20 - API-610 Nozzle Output Report Segments
Chapter 6 Technical Discussions 6-129
Notice in Figure 20, that each report segment indicates which values are related to the global coordinate system and which
are related to the local API coordinate system.
Transforming from Global to Local
Converting (or transforming) values from the CAESAR II global coordinate system to a local coordinate system involves
applying a number of rotation matrices to the global values. Matrix mathematics is not a trivial task, and one must exercise
the utmost care to arrive at the correct result. For those that want to undertake this task themselves, a utility (discussed in
the July 2001 issue of COADEs Mechanical Engineering News) can be downloaded from the COADE website to perform
this transformation. The use of this utility (GlbtoLocal) is illustrated here, using the nozzle at node 50 as an example.
The element 40-50 is defined with the delta coordinates of:
DX = 3 ft. 6.426 in
DY = -3 ft. 6.426 in
DZ = 0.0
The global restraint forces at node 50, in global coordinates, for the operating case are:
FX = 323. MX = -953.
FY = 4. MY = -9.
FZ = -271. MZ = -548.
Using this data as input to GlbtoLocal, the utility yields the forces on the restraint in the elements local coordinate system.
This is shown in Figure 21 below.
Figure 21 - Example Global to Local Transformation
The set of values labeled Rotated Displacements / Load Vector can be compared with the Local Element Force /
Moment report, as shown in Figure 18. Note however, that a change in sign is necessary, since the restraint report shows
loads acting on the restraint, while the element report shows loads acting on the element.
6-130 Technical Discussions
Frequently Asked Questions
What are global coordinates? Global coordinates defines the mapping of a physical system into a mathematical system.
For any given model, the global coordinate system is fixed for the entire model. In CAESAR II, there are tow alternative
global coordinate systems that can be applied to a model. Both coordinate systems follow the "right hand rule" and use "X",
"Y", and "Z" as mutually perpendicular axes. The first uses the "Y" axis vertical, while the second uses the "Z" axis as
vertical.
What are local coordinates? Local coordinates represent the mapping for a single element. Local coordinate systems are
used to define positive and negative directions and loads on elements. Local coordinate systems are aligned with the
elements, and therefore vary throughout the model.
What coordinates are used to plot and view the model? The model's global coordinate system is used to generate plots of
the model. This is necessary since each element has its own local coordinate system, and these local systems can vary from
element to element. Local coordinate systems are an element property, not a system property.
How do you obtain restraint loads in local coordinates? In general, you don't - this doesn't make any sense. Restraint
loads are a nodal property. Nodes don't have local coordinate systems, elements do. While an argument can be made that the
local coordinate system of the connecting element should be used, this is only valid if one single element frames into the
restraint. As soon as multiple elements frame into the restraint, there are multiple local coordinate systems to deal with. The
lone exception is when a single element frames into a nozzle. In this instance, the restraint loads in this single element's
coordinate system can be obtained from the element's local force/moment report, with a change in sign.
How do you obtain nodal displacements in local coordinates? In general, you don't - this doesn't make any sense.
Displacements are a nodal property. Nodes don't have local coordinate systems, elements do. Refer to the preceding
discussion on restraint loads for additional details.
What do you do with local coordinates? In most instances nothing. The only time local coordinates are useful in CAESAR
II is when dealing with a skewed nozzle. The CAESAR II software interface makes the use of local coordinates unnecessary
except in this one instance.
Chapter 7 Miscellaneous Processors
This chapter discusses the processors that are available in CAESAR II.
In This Chapter
Accounting............................................................................................... 7-2
Batch Stream Processing ......................................................................... 7-7
CAESAR II Fatal Error Processing ......................................................... 7-9
Units File Operations............................................................................... 7-10
Convert Input to New Units..................................................................... 7-13
Material Database .................................................................................... 7-14
C H A P T E R 7
7-2 Miscellaneous Processors
Accounting
The CAESAR II accounting system has the following characteristics:
Its use is optional. Users not wishing to keep accounting records of their runs never need to know that an accounting
capability exists.
Users conveniently control all pricing factors. The total price of any job is computed from:
IF (C4 > 0.0) THEN
cost = C1*cputime + (C2*nodes + C3*elements) * C4 * numcases + C5
ELSE
cost = C1*cputime + (C2*nodes + C3*elements) + C5
ENDIF
Users enter C1, C2, C3, C4, and C5 one time, and changes them only when needed.
Any of the constants may be zero but at least one must be greater than zero.
Accounting reports are generated on a per run basis and are summarized on a per account basis.
Reports may be generated for any user requested combination of account numbers.
Account numbers are user-defined and may be up to 25 alphanumeric characters.
Account and program access can be controlled through the accounting system via optional password protection.
Account numbers can be identified for each job using either of two methods:
Account number must be selected from a displayed table of allowed account numbers, or will default to the last valid
account number input. The account number table is set up and maintained by the account manager.
Account number must be some non-blank string. There is no default, and the users entry must match one of the allowed
account numbers input previously by the account manager. Access to the available account number list is password
protected. Users not having valid account numbers will not be permitted to run.
Generated reports contain:
Account number
Jobname
Time and Date of Run
Number of Nodes, Elements, and Load Cases
Calculated Job Cost
Accounting summary reports include subtotals on a per account number basis, the number of jobs run under the
account, and the time period the account has been active.
The accounting system is delivered in an uninitialized state. To use the accounting system, users must change this state to
active. (It may later be deactivated if the user does not want to use the account record-keeping feature.) To activate the
accounting system from the CAESAR II Main Menu, select TOOLS - ACCOUNTING. The Accounting dialog displays.
Chapter 7 Miscellaneous Processors 7-3
Select the applicable accounting method (either type 1 or type 2) and then click the Activate Accounting button. The user
will receive a that it is indeed activating the accounting as requested. Next set the Pricing Factors by selecting the next tab
in the window to show the sheet as displayed below.
7-4 Miscellaneous Processors
Users should enter any costs as appropriate; blanks are allowed. Each rate is multiplied by the respective job quantity, and
the sum of these products is equivalent to the job cost. Job costs are calculated on an integer dollar basis, and will never be
less than one dollar. Any of the 5 rate constants can be zero, but not all; and none of the constants may be negative.
Account numbers are entered under the Account Numbers tab as shown below. These are the numbers that will be used to
prompt users for an account number during program execution. Be sure to click the Save button before exiting!
Once the accounting system is initialized and the pricing factors are set, users can return to the CAESAR II Main Menu and
initiate jobs with account tracking. The prompt for the account number will appear during analysis, immediately after the
user starts a CAESAR II execution. If type 2 accounting is implemented then users must match the appropriate account
number exactly, whereas all account numbers will be displayed in a list box if type 1 accounting has been activated.
Chapter 7 Miscellaneous Processors 7-5
The prompt for accounting information requires user-account identification.
For type 2 accounting users are expected to enter a valid account number, or click OK for the default (last used) account
number. For type 1 accounting users select the appropriate account number from the list and click OK to continue.
An example Accounting report displays below:
7-6 Miscellaneous Processors
Accounting File Structure
The format of the CAESAR II accounting file is structured so that users may write a program to access and/or manipulate this
file. The name of the CAESAR II accounting file is ACCTG.DAT. This file contains all of the information used by CAESAR II
to produce accounting reports. The accounting file may be opened (in FORTRAN) with the following:
OPEN(1,FILE=ACCTG.DAT,STATUS=OLD,FORM=BINARY, ACCESS=DIRECT,RECL=55)
The following information is stored on each record:
Variable Type Definition
JOBNAME CHARACTER*8 Name of the job being run.
ICPUTIME INTEGER*4 Analysis CPU time used (Seconds)
NODES INTEGER*2 Number of nodes in the job
NELEMS INTEGER*2 Number of elements in the job
NLOADS INTEGER*2 Number of load cases in the job
MYEAR INTEGER*2 Year the job was run
MMONTH INTEGER*2 Month the job was run
MDAY INTEGER*2 Day of the month the job was run
MHOUR INTEGER*2 Hour of the day the job was run
MMINUTE INTEGER*2 Minutes of the hour when the job was run
MSECOND INTEGER*2 Seconds of the minute when the job was run
ACCOUNTNO CHARACTER*25 Account number to be billed for job
The first record contains only a single integer value (ILAST) giving the last valid record number in the accounting file. The
number of job entries is equal to (ILAST-1). This first record may be read:
READ(1,REC=1) ILAST
Chapter 7 Miscellaneous Processors 7-7
Batch Stream Processing
The Batch Stream Processor is a module which allows users to analyze multiple jobs, in batch mode. This enables users to
instruct the computer to run up to twelve different jobs completely unattended. The following are the requirements to
properly initiate a batch stream process:
The jobs must all be located in the same data directory, and the Default Data Directory must be set to this directory.
The jobs must be ready to run. This means that the jobs must have successfully passed error checking and static and
dynamic load cases have been defined. If the static load cases have not been defined, CAESAR II uses the standard
recommended cases.
Accounting should be turned off, or set so that a default account number can be assumed by the program.
Adequate disk space must be available to generate the scratch and output files for all of the jobs.
Users can enable the Batch Stream Processor from the CAESAR II MAIN MENU by clicking TOOLS - MULTI- JOB ANALYSIS.
The Define Jobs to Run button enables users to define the names and job types to be executed in the stream. The job names
are the usual CAESAR II job names that the user has prepared for analysis. The job name specification screen is shown in the
following figure.
7-8 Miscellaneous Processors
Once the job names (up to forty) have been specified, click the OK button. The Batch Stream window returns. Clicking the
Analyze Specified Jobs button will start the analysis of all previously defined jobs.
The user does not have to analyze the jobs immediately. The job names and analysis types are stored in a data file,
BATCH.STM, which can be invoked at any time by the user. When the user is ready, the Batch Stream Processor can be
started and the analyze option invoked. The user can then leave the computer, and return to review the output at a later
time.
The Batch Stream Processor creates a log file of its progress so that users have an idea of how long the process took, or
can diagnose any failures in the batch process. This log file is named BATCH.LOG and can be found in the directory with
the jobs. This file is a standard ASCII text file which can be edited or printed.
Chapter 7 Miscellaneous Processors 7-9
CAESAR II Fatal Error Processing
Every effort has been made to alert the user that data may be inconsistent or unusual for the type of analysis being
attempted. However, there exists the potential for user modeling techniques or hardware/operating system problems to
generate an error condition within the CAESAR II computation routines. Recognizing this potential, internal self checks are
performed by CAESAR II to trap these abnormal conditions. (Examples of abnormal conditions are: full hard disks, invalid or
expired ESLs, file corruption, insufficient free memory, etc.)
Whenever a fatal error condition arises, CAESAR II will abort the current process. However, CAESAR II attempts to provide
the user with an explanation of what went wrong to cause the process to be aborted. This is accomplished in several stages
as outlined in the following discussion.
First, each error trap/condition is assigned a unique number. When an abort condition occurs, this error number and a short
description of the error are displayed in a window. An example of such a message is given in the next figure.
When the OK button is clicked the error text window is closed and the user has the option of referencing further error
information. (This may be desirable when one error definition references another.) The OK button from the additional error
information window returns program control to the main CAESAR II Main Menu. This additional error information may be
called upon at any time from the CAESAR II Main Menu by selecting the DIAGNOSTICS-ERROR REVIEW menu option.
7-10 Miscellaneous Processors
Units File Operations
The active units file as specified in the configuration file is used in conjunction with all new input files and all existing
output files in the given data directory. The units file specified in the configuration file will not modify the units in an
existing CAESAR II input file Convert Input to New Units.
Make Units File
The user may create a custom units file or review an existing unit's file by choosing TOOLS /MAKE UNITS FILE from the
CAESAR II Main Menu. An explanation of each input field and button under this option follows.
Review Existing Units File
Make Units File Dialog
Clicking the Review Existing Units File button highlights a list box to the right that contains all existing units files located
in both the data directory and the program directory. Choose the units file to review from the list, then click the View/Edit
File button to proceed. A window will display (see below) containing all CAESAR II dimensional items, their internal units,
the conversion factor between the internal units and the user-specified units, and the users units.
Chapter 7 Miscellaneous Processors 7-11
Review Existing Units Dialog
Create a New Units File
Units Maintenance
Clicking the Create a New Units File button creates a new units file and activates the next two items described below.
When all items are completed choose the View/Edit File button to proceed. A window will appear in which the entries for
the user's units and the conversion factor can be edited. If the user-defined units for a given item exist in the list then there is
no need to choose a conversion factor, as it will be updated automatically. If a new set of units is desired (miles in the length
category for instance) then the user may type in (or select from the drop down list) the new unit name (mi.) and the new
conversion factor (.00001578 in this example).
7-12 Miscellaneous Processors
Create New Units Dialog
Existing File to Start From
In CAESAR II a new units file is created by using an existing units' file as a template. Choose an existing units' file from the
list. It is simplest to choose a file that has many units in common with the file to be created.
New Units File Name
A unique file name must be entered here without the extension.
View/Edit File
Click this button to proceed once all activated lists on the Create New Units dialog have been completed.
Chapter 7 Miscellaneous Processors 7-13
Convert Input to New Units
The user may convert an existing input file to a new set of units by choosing TOOLS / CONVERT INPUT TO NEW UNITS from the
CAESAR II Main Menu. A window will be created that contains the following three input fields:
Units File Conversion Dialog
Name of the Input File to Convert
Type the full path name followed by the input file name (including the ._a extension) to be converted. The Browse button to
the right of this text box may be used to choose the appropriate input file.
Name of the Units File to Use
Select the name of the appropriate units file from the list provided.
Name of the Converted File
Type the full path name followed by the input file name that corresponds to the new input file.
Caution: Clicking the Browse button here and picking an existing ._a file the converted file will overwrite the existing ._a
file chosen from the list.
7-14 Miscellaneous Processors
Material Database
CAESAR II provides a material database (accessed with TOOL/MATERIAL DATABASE from the MAIN MENU listing physical properties
and code-dependent allowable stresses of more than 300 materials. These materials can be edited and additional materials
can be added to the database by the user.
Note: It is incumbent upon the user to check material allowables and other physical property data for the particular code
being used. While COADE attempts to keep the material database up-to-date the codes are subject to change frequently and
the accuracy of the database is not guaranteed. Below is an explanation of the input fields for the Material Database.
Material - Add
This option enables users to add a new material spreadsheet to the database. This command saves any data currently shown
on the spreadsheet and clears the spreadsheet for a new entry. At least a material number and code must be given for the
data to be saved.
NOTE: When adding a new material to the database, two entries should be made. The first entry should be associated with
"All Codes", and includes all data except for the allowable stresses. After "saving" this entry, the Piping Code can be
changed and the allowable stresses defined. It is the "All Codes" entry that is listed in the "drop list" for material selection
in the Piping Input processor.
Material - Delete
This operation deletes the entire material spreadsheet from the database. The user may choose the spreadsheet to delete from
the list, which contains only user-defined database spreadsheets. The user cannot delete the material database spreadsheets
supplied with CAESAR II.
Chapter 7 Miscellaneous Processors 7-15
Material - Edit
This option enables users to edit an existing material spreadsheet in the database. A window will appear from which the user
must either enter the name of the material or pick the material from the list. The piping code ID on the right side
corresponds to the piping code ID on the piping input spreadsheet when allowables are chosen.
Material Database Editor Displaying Data for A106-B
Number
Enter a number by which the material is to be referenced. The number must be between 101 and 699 inclusive and should
not already be a reference for another material.
Name
Enter the material name as listed in the applicable code.
Eff, Cf, z
This factor is necessary for various piping codes as defined below:
STOOMWEZEN - The cyclic reduction factor, referred to in the code as Cf.
NORWEGIAN - This is the circumferential weld strength factor, z. If not entered, it defaults to 1.0.
7-16 Miscellaneous Processors
BS 7159 - This field is the ratio of the design stress sd, in the circumferential (hoop) direction to the design stress in the
longitudinal direction. Since design stress is defined in Sec. 4.3 of the code as:
o
d
= e
d
* E
lam
, s
d x
= ed * E
lamx
and design strain should be the same for both directions, this entry will also be the ratio of the moduli of elasticity
E
lam
(hoop) to E
lamx
(longitudinal).
If left blank, a value of 1.0 will be used.
Applicable Piping Code
Enter the CAESAR II piping code for the material. A list of the piping codes supported by CAESAR II display below:
ALL B31.5 NAVY 505 Stoomwezen FDBR
B31.1 B31.8 CAN Z662 RCC-M C BS 7159
B31.1 1967 B31.11 BS 806 RCC-M D UKOOA
B31.3 ASME NC Swedish 1 CODETI IGE/TD/12
B31.4 ASME ND Swedish 2 Norwegian TBK-6 DNV
EN-13480 GPTC/Z380 PD-8010-1 PD-8010-2 ISO-14692
Density
Enter the density of the material.
Minimum Temperature Curve (A-D)
As defined by B31.3 (Section 323.2.2), some carbon steels are limited to a minimum metal temperature as shown in
Figure 323.2.2. This cell is used to specify which curve should be used to check this material. If this code section is
applicable, specify either A, B, C, or D. If this code section is not applicable, leave this cell blank. Note that CAESAR II
does not currently use this information.
FAC
A factor necessary for various piping codes as defined below:
StoomwezenThis value should be either 0.44 or 0.5 and is used in computing the equilibrium stresses as discussed in
Section 5.2 of the code. The value of 0.5 can be used for steel if the design and fabrication are such that stress peaks are
avoided.
Norwegian Material ultimate tensile strength at room temperature R
m
. If not entered, this factor is not considered to
control the expansion stress allowable.
Poisson's Ratio
Thus input is for Metals only. Enter the value to be used for Poissons Ratio for this material.
Temperature
In this field enter the temperatures corresponding to the database values you will add to the right. In the database supplied
with CAESAR II all temperatures are in 100F increments. Note that some of the codes list physical property values in 50F
increments, therefore small discrepancies may occur between CAESAR II and a given code because of the interpolation of
data.
Chapter 7 Miscellaneous Processors 7-17
Exp. Coeff.
Enter the expansion coefficient at the corresponding temperature. This coefficient must be multiplied by 10
6
F prior to being
input here. (ex. An expansion coefficient of 1.2 x 10
-5
in/in/F would be input as 12).
Allowable Stress
Input the code allowable stress corresponding to the temperature to the left.
Elastic Modulus
This is the Modulus of Elasticity corresponding to the temperature to the left.
Yield Stress
This is the Yield Stress corresponding to the temperature to the left.
Ult Tensile Stress
BS 806Mean Stress to Failure for design life at temperature
Swedish Method 1Creep Rupture Stress at temperature.
StoomwezenRr
g
average creep stress to produce 1% permanent set after 100,000 hours at temperature (vm).
IGE/TD/12 Ultimate Tensile Strength
Norwegian(UNITS: lb./sq.in.) The Material ultimate tensile strength at room temperature is "Rm". If not entered, this
factor is not considered to control the expansion stress allowable.
Chapter 8 Interfaces
This chapter lists the programs with which CAESAR II interfaces and explains how the interfaces work.
In This Chapter
Overview of CAESAR II Interfaces ........................................................ 8-2
CAD Interfaces ........................................................................................ 8-4
Generic Neutral Files............................................................................... 8-57
Computational Interfaces......................................................................... 8-76
Data Export to ODBC Compliant Databases........................................... 8-81
C H A P T E R 8
8-2 Interfaces
Overview of CAESAR II Interfaces
There are several external interfaces in existence which allow data transfer between CAESAR II and other software packages.
These interfaces can be accessed via the Tools menu item on the CAESAR II Main Menu. Choosing the External Interface
menu item exposes an additional menu shown below from which many interface packages are available.
These interfaces are the means through which CAESAR II data is accepted from other sources, or data generated in CAESAR II
is provided to other packages. For the most part, this data transfer is from a drawing or analysis package to CAESAR II. The
CAESAR II Neutral File transfers both to and from CAESAR II, and the AUTOCAD interface only transfers CAD data from
CAESAR II.
Note CADWorx Plant provides a seamless, bi-directional interface between AutoCAD and CAESAR II, but does not have to
go through a translation procedure.
1 Most of the interfaces are CAD interfaces. The exceptions are: LIQT, PIPENET, the C2DAT Matrix, and the CAESAR II
Neutral File.
2 The CAD interfaces are intended to transfer the piping geometry into CAESAR II. The resulting CAESAR II input must be
thoroughly checked, with loads, restraints, and other specifics added.
Chapter 8 Interfaces 8-3
3 The interface labeled CAESAR II Neutral File is the only interface (aside from CADWorx Plant) that is capable of
transferring 100% of the data which comprises the _A (input) file.
4 PRO-ISO, CADPIPE, and AutoPlant are not stand-alone CAD packages. Instead, these are intelligent symbols libraries
for use with AutoCAD. The interface out to AutoCAD does not utilize any of these three packages; it just creates a
DXF file.
5 LIQT is a transient analysis package for liquids in piping networks, and can calculate pressure imbalances as a function
of time. This LIQT output is converted by the CAESAR II interface to create force response spectra for CAESAR II
dynamic input.
6 PIPENET is a transient analysis package for liquids in piping networks, and can calculate pressure imbalances as a
function of time. This PIPENET output is converted by the CAESAR II interface to create a CAESAR II dynamic input file
for a force response spectrum analysis.
7 The interfaces typically prompt the user for a file name, transfer the data, and then prompt for another file name. This
circular procedure is continued until a blank file name is encountered or the user presses the Cancel button.
8 Users and third party developers beginning an interface to CAESAR II are urged to follow the requirements of the
CAESAR II Neutral File interface, since this will enable all of the spreadsheet data to be transferred.
9 CADWorx Plant is COADE's piping design and drafting program for the AutoCAD environment. Data may be completely
and seamlessly transferred between CAESAR II and CADWorx Plant, without creating any neutral files or going through
any intermediate steps.
8-4 Interfaces
CAD Interfaces
CADWorx Plant Link
CADWorx is an AutoCAD based design/drafting program (developed by COADE) with a bi-directional data transfer link to
CAESAR II. CADWorx allows models to be created in ortho, iso, 2D, or 3D modes. Models constructed in CADWorx can be
sent into CAESAR II, and models built in CAESAR II can be sent into CADWorx. Modifications made in either program are
retained for future transfers.
In addition, CADWorx allows CAESAR II output data to be imported and placed on the drawing. This provides the ability to
generate stress and restraint isometrics.
Since the interface operates seamlessly, no action need be taken on the CAESAR II sideCADWorx Plant simply uses
CAESAR II _A (input) and _P (output) filesso the CADWorx Plant option on this menu serves only as a reminder. For
more information on importing and exporting CAESAR II files to and from CADWorx Plant, refer to that product's User
Manual.
DXF AutoCAD Interface
Once a job has successfully passed error checking, its geometric information can be converted into an AutoCAD DXF file
using the CAESAR II External Interface Module. The job must pass the error checker, since several of the execution files
created by the error checker are used. To generate an AutoCAD DXF file simply choose the AUTOCAD DXF FILE menu item,
enter the name of the job to be converted into a DXF file when prompted, and click OK on the dialog box.
When the file conversion is complete, the program will prompt for another job name. This cycle will be repeated until the
Cancel button is clicked. Next, the user should copy all of the just created DXF files into the AutoCAD subdirectory.
Start AutoCAD as normal, begin a new drawing, and enter a drawing name. The BEGIN NEW DRAWING option must be selected.
At the first prompt, issue the DXFIN command. This will cause AutoCAD to prompt for the file tp read. When reading the
specified file, AutoCAD will rescale and display the model. To access the COADE supplied LISP routines, which scale node
numbers, a LISP file must be loaded. The command to accomplish this is (load "NODSIZ").
Note: The parentheses in the previous command are required.
Information about pipes and node points can be obtained by using the LIST command. The ATTDISP command can be used
to turn on/off the attribute display, which at this point consists of only node numbers. the size of the node numbers can be
changed by using the LISP routine NODSIZ. To resize the node numbers, simply enter NODSIZ, and answer the prompts.
To resize the node numbers, simply enter NODSIZ and answer the prompts.
In order for this interface program to function properly, all of the intermediate data files, generated by the CAESAR II
Error Checker, must be present. This is the only problem that has ever terminated this interface program.
CADPIPE Interface
The interface between CAESAR II and CADPIPE is a one-way transfer of the geometry data from CADPIPE to CAESAR II.
The geometry data consists of the pipe lengths, diameters, thicknesses, connectivities, and node numbers. All nodal specific
quantities (restraints, loads, displacements, etc.) must be added to the CAESAR II input file in the usual manner by the user.
The CADPIPE interface is set up so that several models can be transferred in a single session. The first prompt is for the
name of the CADPIPE connectivity (.UDE ) neutral file. Once the user specifies this file name, the transfer process occurs
and the interface program prompts for another neutral file name. This is an endless cycle until the user terminates with the
Cancel button.
Chapter 8 Interfaces 8-5
The neutral file read by the interface program must be generated by the CADPIPE program. Details of this step can be
found in the CADPIPE documentation. The CADPIPE neutral file must be transferred into the CAESAR II directory so that it
is available to the interface program.
The interface program reads the CADPIPE neutral file and generates the CAESAR II input file and a log file of the transfer
process. Users should check the data in both the CAESAR II input file and the log file for consistency and any assumptions
made by the interface. The following paragraphs describe the layout of the data extracted from the CADPIPE neutral file
and how it is arranged for storage in this interface program. The data storage is maintained in two arrays, the first contains
geometry data for each pipe element, the second array contains additional loading and specification data.
In the first array, an entry is required for each piece of pipe in the system. A pipe in this sense is an entity between two
nodes, which could be a pipe, or a rigid element. There are 12 values per entry, where all values must be specified.
Field 1 - ELMT
This is the pipe element number, which may correspond to an entry in the second array. This is also the pipe/element
number in the model. These values should be sequential from 1.
Field 2 - N1
This is the FROM node number, i.e. the starting node for the element. These values must be greater than zero and less
than 32000.
Field 3 - N2
This is the TO node number, i.e. the ending node for the element. These values must be greater than zero and less than
32000.
Field 4 - DX
This is the delta X dimension for the element. This is the distance between N1 and N2 in the X direction.
Field 5 - DY
This is the delta Y dimension for the element. This is the distance between N1 and N2 in the Y direction. In CAESAR II,
Y is vertical.
Field 6 - DZ
This is the delta Z dimension for the element. This is the distance between N1 and N2 in the Z direction.
Field 7 - DIAM
This is the pipe outer diameter.
Field 8 - THK
This is the pipe wall thickness.
Field 9 - ANCH
This is a restraint (support) indicator flag. If ANCH is 1, then there is a restraint on N1. If ANCH is 2, then there is a
restraint on N2. The type of restraint can be obtained from the second array.
Field 10 - BND
8-6 Interfaces
This field indicates the presence of a bend at the N2 end of the element. If BND is 1, there is a bend at N2. If BND is 0, this
is a straight pipe.
Field 11 - BRAD
This field is used to specify the bend radius if the bend is not a long radius bend. The value here should be the desired bend
radius.
Field 12 - RIGD
This field is a flag used to indicate that the current element is a rigid element. The weight of the element can be obtained
from the second array.
Records in the second array are only necessary when additional data is required. This means there will always be a record in
first array for pipe element #1 (this could be the only entry in the array). Any additional entries will contain some type of
change to data normally duplicated forward by CAESAR II.
Field 1 - ELMT
This is the pipe element number, which corresponds to an entry in the first array. This is also a pipe/element number in the
model. These numbers are sequential from 1.
Field 2 - TEMP1
This is the operating temperature for load case 1, found by scanning the CADPIPE data for the maximum temperature.
Field 3 - PRESS1
This is the operating pressure for load case 1, found by scanning the CADPIPE data for the maximum pressure.
Field 4 - RGDWGT
This value is the weight of rigid elements. This entry is only required if the RIGID flag was set in the first array.
Field 5 - TEEFLG
This value indicates the TEE type.
1 - reinforced
2 - unreinforced
3 - welding tee
4 - sweepolet
5 - weldolet
6 - extruded welding tee
Field 6 - RESTYP
This value is the restraint (support) type indicator. Type values are:
0 - anchor
Chapter 8 Interfaces 8-7
1 - double acting X
2 - double acting Y
3 - double acting Z
4 - double acting RX
5 - double acting RY
6 - double acting RZ
Field 7 - RINFO1
Data for supports, by default, the restraint stiffness.
Field 8 - RINFO2
Data for supports, by default, the restraint gap.
Field 9 - RINFO3
Data for supports, by default, the restraint friction coefficient.
Field 10 - MATID
The CAESAR II material ID value. Note that if the coefficient of expansion is to be changed, it should be entered in the
Temperature field above (Field 2).
Field 11 - EMOD
The value of Youngs modulus.
Field 12 - POIS
The value of Poissons ratio.
Field 13 - GAMMA
The weight density of the material.
Field 14 - INSTHK
The insulation thickness.
Field 15 - INSWGT
The weight density of the insulation material.
Field 16 - FLDWGT
The weight density of the pipe contents (fluid).
Field 17 - TEENOD
8-8 Interfaces
The element node number where there is a tee.
Field 18 - (Placeholder for future development.)
Field 19 - (Placeholder for future development.)
Field 20 -(Placeholder for future development.)
CADPIPE Example Transfer
The following is an example connectivity file produced by the CADPIPE program. Examination of this file reveals two
distinct regions. The first region defines the entities which make up the piping system, while the second region connects the
entities. Both regions are required for the interface to work properly. The first line of each entity definition contains various
codes which define: the element type, the element diameter, and the element thickness.
BEGIN_ENTITY
ENTITY_NUMBER 1
ATTRIBUTES 1CAESAR AAA1 C-2OBB1dLATL
INSERTION 1.80000000e+002 3.36000000e+002 1.20000000e+003
END 1.80000000e+002 3.36000000e+002 1.20000000e+003
END 1.80000000e+002 3.35999961e+002 1.20350000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 2
ATTRIBUTES 1CAESAR AAA1 C-2OPPATLATL 134.50
INSERTION 1.80000000e+002 3.35999997e+002 1.27075000e+003
END 1.80000000e+002 3.35999961e+002 1.20350000e+003
END 1.80000000e+002 3.36000033e+002 1.33800000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 3
ATTRIBUTES 1CAESAR AAA1 C-3O1BATLATL
INSERTION 1.80000000e+002 3.36000000e+002 1.34700000e+003
END 1.89000000e+002 3.36000000e+002 1.34700000e+003
END 1.80000000e+002 3.36000033e+002 1.33800000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 4
ATTRIBUTES 1CAESAR AAA1 C-0OPPATLATL 105.38
INSERTION 2.41687500e+002 3.35999959e+002 1.34700000e+003
END 1.89000000e+002 3.36000000e+002 1.34700000e+003
END 2.94375000e+002 3.35999917e+002 1.34700000e+003
END_ENTITY
Chapter 8 Interfaces 8-9
BEGIN_ENTITY
ENTITY_NUMBER 5
ATTRIBUTES 1CAESAR AAA1 C-0O2HATLATLATL
INSERTION 3.00000000e+002 3.36000000e+002 1.34700000e+003
END 3.05625000e+002 3.36000083e+002 1.34700000e+003
END 2.94375000e+002 3.35999917e+002 1.34700000e+003
END 3.00000083e+002 3.30375000e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 6
ATTRIBUTES 1CAESAR AAA1 C-0O1BATLATL
INSERTION 4.02000000e+002 3.36000000e+002 1.34700000e+003
END 3.93000000e+002 3.35999934e+002 1.34700000e+003
END 4.01999934e+002 3.45000000e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 7
ATTRIBUTES 1CAESAR AAA1 C-0OPPATLATL 90.00
INSERTION 4.02000017e+002 3.90000000e+002 1.34700000e+003
END 4.01999934e+002 3.45000000e+002 1.34700000e+003
END 4.02000099e+002 4.35000000e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 8
ATTRIBUTES 1CAESAR AAA1 C-3O1BATLATL
INSERTION 4.02000000e+002 4.44000000e+002 1.34700000e+003
END 4.02000099e+002 4.35000000e+002 1.34700000e+003
END 4.02000033e+002 4.44000000e+002 1.33800000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 9
ATTRIBUTES 1CAESAR AAA1 C-2OBB1dLATL
INSERTION 4.02000000e+002 4.44000000e+002 1.20000000e+003
END 4.02000000e+002 4.44000000e+002 1.20000000e+003
END 4.02000000e+002 4.43999961e+002 1.20350000e+003
END_ENTITY
BEGIN_ENTITY
8-10 Interfaces
ENTITY_NUMBER 10
ATTRIBUTES 1CAESAR AAA1 C-2OPPATLATL 134.50
INSERTION 4.02000017e+002 4.43999981e+002 1.27075000e+003
END 4.02000000e+002 4.43999961e+002 1.20350000e+003
END 4.02000033e+002 4.44000000e+002 1.33800000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 11
ATTRIBUTES 1CAESAR AAA1 C-0O1BATLATL
INSERTION 3.00000000e+002 2.16000000e+002 1.34700000e+003
END 2.99999967e+002 2.25000000e+002 1.34700000e+003
END 3.09000000e+002 2.16000033e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 12
ATTRIBUTES 1CAESAR AAA1 C-0OPPATLATL 105.38
INSERTION 3.00000025e+002 2.77687500e+002 1.34700000e+003
END 2.99999967e+002 2.25000000e+002 1.34700000e+003
END 3.00000083e+002 3.30375000e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 13
ATTRIBUTES 1CAESAR AAA1 C-0OPPATLZTL 69.00
INSERTION 3.43500000e+002 2.16000017e+002 1.34700000e+003
END 3.09000000e+002 2.16000033e+002 1.34700000e+003
END 3.78000000e+002 2.16000000e+002 1.34700000e+003
END_ENTITY
BEGIN_ENTITY
ENTITY_NUMBER 14
ATTRIBUTES 1CAESAR AAA1 C-0OPPATLATL 87.38
INSERTION 3.49312500e+002 3.36000008e+002 1.34700000e+003
END 3.05625000e+002 3.36000083e+002 1.34700000e+003
END 3.93000000e+002 3.35999934e+002 1.34700000e+003
END_ENTITY
BEGIN_RUN
LINE_NUMBER CAESAR AAA1
BEGIN_COORD 1.80000000e+002 3.00000000e+002 1.20000000e+003
END_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
Chapter 8 Interfaces 8-11
BEGIN_SEGMENT
BEGIN_COORD 1.80000000e+002 3.00000000e+002 1.20000000e+003
END_COORD 1.80000000e+002 3.36000000e+002 1.20000000e+003
ENTITY 1
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 1.80000000e+002 3.36000000e+002 1.20000000e+003
END_COORD 1.80000000e+002 3.36000000e+002 1.34700000e+003
ENTITY 1
ENTITY 2
ENTITY 3
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 1.80000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
ENTITY 3
ENTITY 4
ENTITY 5
END_SEGMENT
END_RUN
BEGIN_RUN
LINE_NUMBER CAESAR AAA1
BEGIN_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 3.78000000e+002 2.16000000e+002 1.34700000e+003
BEGIN_SEGMENT
BEGIN_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 3.00000000e+002 2.16000000e+002 1.34700000e+003
ENTITY 5
ENTITY 12
ENTITY 11
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 3.00000000e+002 2.16000000e+002 1.34700000e+003
END_COORD 3.78000000e+002 2.16000000e+002 1.34700000e+003
ENTITY 11
ENTITY 13
END_SEGMENT
8-12 Interfaces
END_RUN
BEGIN_RUN
LINE_NUMBER CAESAR AAA1
BEGIN_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 4.44000000e+002 4.44000000e+002 1.20000000e+003
BEGIN_SEGMENT
BEGIN_COORD 3.00000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 4.02000000e+002 3.36000000e+002 1.34700000e+003
ENTITY 5
ENTITY 14
ENTITY 6
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 4.02000000e+002 3.36000000e+002 1.34700000e+003
END_COORD 4.02000000e+002 4.44000000e+002 1.34700000e+003
ENTITY 6
ENTITY 7
ENTITY 8
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 4.02000000e+002 4.44000000e+002 1.34700000e+003
END_COORD 4.02000000e+002 4.44000000e+002 1.20000000e+003
ENTITY 8
ENTITY 10
ENTITY 9
END_SEGMENT
BEGIN_SEGMENT
BEGIN_COORD 4.02000000e+002 4.44000000e+002 1.20000000e+003
END_COORD 4.44000000e+002 4.44000000e+002 1.20000000e+003
ENTITY 9
END_SEGMENT
END_RUN
As the interface runs, status messages are displayed on the users terminal for informative purposes. Once the transfer is
complete, the user should review the .LOG file generated to insure that there are no unexplained errors or warnings. The
.LOG file generated for the above .UDE file is listed as follows.
Chapter 8 Interfaces 8-13
*** CAESAR II / CADPIPE Geometry Translator ***
CADPIPE data as read in for NEUTRAL file: NRGTST1.UDE
General Notes
This file contains the status of the data conversion from the CADPIPE ISO system to the CAESAR II stress analysis package.
The data contained in this file is grouped into three sections:
1 Entity information
2 Segment connectivity information
3 Final interpreted CAESAR II data.
Anomalies with final CAESAR II model geometry should be traced through this file, possibly back to the CADPIPE
connectivity file. Notes and warning messages are shown below as necessary.
Since all required CAESAR II data is not available in the CADPIPE environment, CAESAR II must make certain modeling
assumptions. Users are cautioned to verify the following assumptions:
1 Thicknesses of .05 are program generated because no match could be found in the standard CAESAR II
diameter/thickness tables. This value must be corrected once in CAESAR II.
2 Rigid elements are assumed to have a weight of 1.0. This value should be corrected once in CAESAR II.
3 Temperatures, pressures, and other loading items are not available for transfer by the interface.
4 Restraint information is not available for transfer by the interface.
5 Material #1 (low carbon steel) is assumed by the interface program.
Error Code Definitions
1 The item code for this entity indicates that it is a custom bend. This interface will make the transfer assuming it is a
long radius elbow. The correction to the proper radius must take place on the CAESAR II spreadsheet.
2 The item code for this entity indicates that it is a mitered bend. This interface will make the transfer assuming it is a
long radius elbow. The correction to the proper radius and number of cuts must take place on the CAESAR II
spreadsheet.
3 The item code for this entity indicates that it is some type of "OLET" fitting. Since there is only a single reference to
this entity in the CADPIPE neutral file, this segment will be discontiguous with the rest of the model in CAESAR II. This
interface will attempt to connect the "OLET" as it sees fit. The final geometry should be checked!
4 The item code for this entity is unknown to the current version of the interface. The entity will be set to a 2 node, zero
length rigid element. The user must modify the CAESAR II data to correct this anomaly.
5 The segment being processed referenced and ENTITY that was not defined in the "ENTITY Information " section of
the ".UDE" file. This indicates some type of error during the generation of the neutral file. Regenerate the neutral file
before using the interface again.
CADPIPE LOG File Discussion
The .LOG file is very useful in locating problems which may have been encountered by the interface program. The .LOG
file is broken down into the following sections:
8-14 Interfaces
Introduction: A one page summary listing general notes about the interface and defines the error code.
Section 1: Lists the entity information as read from the CADPIPE connectivity file. Note that each entity has been
grouped into one of four possible element types, node numbers have been assigned, and the coordinate system has been
rotated to conform to the standard pipe stress coordinate system (Y vertical).
Section 2: Details the interpretation and model building process.
Section 3: Lists the final transformed data which the interface program wrote as the CAESAR II input file.
A sample .LOG file follows.
Section 1-Entity Information
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
Element types are: 1 - Pipe 2 - Bend 3 - Intersection 4 - Rigid
Interpreted Entity information for: 14 Entities.
Chapter 8 Interfaces 8-15
Section 2-Segment Information
Processing LINE_NUMBER:
CAESAR AAA1
Entity 1 Original nodes: 10. 20.
STARTING new segment with new Entity # 1, FROM node is 10.
CAESAR II type is PIPE
Final nodes: 10. 20.
Finished processing segment with entities: 1
Entity 1 Original nodes: 10. 20.
STARTING new segment with old Entity # 1, FROM node is 20.
CAESAR II type is 1.
Entity 1 PIPE has already been processed. Skip in progress.
Entity 2 Original nodes: 30. 40.
Final nodes: 20. 40.
Entity 3 Original nodes: 50. 60.
Switched TO/FROM orientation.
Final nodes: 40. 50.
Finished processing segment with entities: 1 2 3
Entity 3 Original nodes: 60. 50.
STARTING new segment with old Entity # 3, FROM node is 50.
CAESAR II type is 2.
Entity 3 BEND has already been processed. Skip in progress.
Entity 4 Original nodes: 70. 80.
Final nodes: 50. 80.
Entity 5 Original nodes: 90. 100.
Resetting element 4 TO node from 80. to 100. and adjusting deltas.
Finished processing segment with entities: 3 4 5
Processing LINE_NUMBER: CAESAR AAA1
8-16 Interfaces
Entity 5 Original nodes: 100. 100.
STARTING new segment with old Entity # 5, FROM node is 100.
CAESAR II type is 3.
Entity 5 TEE has already been processed. Skip in progress.
Entity 12 Original nodes: 230. 240.
Switched TO/FROM orientation.
Final nodes: 100. 230.
Entity 11 Original nodes: 210. 220.
Final nodes: 230. 220.
Finished processing segment with entities: 5 12 11
Entity 11 Original nodes: 210. 220.
STARTING new segment with old Entity # 11, FROM node is 220.
CAESAR II type is 2.
Entity 11 BEND has already been processed. Skip in progress.
Entity 13 Original nodes: 250. 260.
Final nodes: 220. 260.
Finished processing segment with entities: 11 13
Processing LINE_NUMBER: CAESAR AAA1
Entity 5 Original nodes: 100. 100.
STARTING new segment with old Entity # 5, FROM node is 100.
CAESAR II type is 3.
Entity 5 TEE has already been processed. Skip in progress.
Entity 14 Original nodes: 270. 280.
Final nodes: 100. 280.
Entity 6 Original nodes: 110. 120.
Final nodes: 280. 120.
Finished processing segment with entities: 5 14 6
Entity 6 Original nodes: 110. 120.
Chapter 8 Interfaces 8-17
STARTING new segment with old Entity # 6, FROM node is 120.
CAESAR II type is 2.
Entity 6 BEND has already been processed. Skip in progress.
Entity 7 Original nodes: 130. 140.
Final nodes: 120. 140.
Entity 8 Original nodes: 150. 160.
Final nodes: 140. 160.
Finished processing segment with entities: 6 7 8
Entity 8 Original nodes: 150. 160.
STARTING new segment with old Entity # 8, FROM node is 160.
CAESAR II type is 2.
Entity 8 BEND has already been processed. Skip in progress.
Entity 10 Original nodes: 190. 200.
Switched TO/FROM orientation.
Final nodes: 160. 190.
Entity 9 Original nodes: 170. 180.
Switched TO/FROM orientation.
Final nodes: 190. 170.
Finished processing segment with entities: 8 10 9
Entity 9 Original nodes: 180. 170.
STARTING new segment with old Entity # 9, FROM node is 170.
CAESAR II type is 1.
8-18 Interfaces
Entity 9 PIPE has already been processed. Skip in progress.
Finished processing segment with entities: 9
Section 3-Final CAESAR II Data
*** C A E S A R I I INTERPRETED GEOMETRY DATA ***
*** C A E S A R I I INTERPRETED PROPERTY DATA *** Part 1
*** C A E S A R I I INTERPRETED PROPERTY DATA *** Part 2
---------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------
Data transferred to CAESAR II array structures.
The CAESAR II job file name is: NRGTST._A
Starting generation of CAESAR II input file for:
13 Elements
4 Bends
0 Rigids
0 Restraints
Conversion of data to CAESAR II completed.
Chapter 8 Interfaces 8-19
Checking the CADPIPE/CAESAR II Data Transfer
It is very important that the resulting CAESAR II input file be verified by the user. The first step in the verification process is
the review of the log file to see if any errors or warnings were generated. The .LOG file is a standard ASCII text file which
can be printed on the system printer or scanned with a text editor. The second step is to enter the input mode of the
CAESAR II program and plot the model. The CAESAR II plot for the CADPIPE example is shown in the following figure.
If the resulting CAESAR II geometry is inconsistent with the CADPIPE drawing, look for the problem in the .LOG file. First,
identify the problem area and locate the relevant elements in Section 3 of the .LOG file. Next, find the appropriate segment
in Section 2 of the .LOG file and ensure it contains the same entities as shown in the CADPIPE connectivity file. Finally,
verify the information in Section 1 of the .LOG file matches the interpreted data in Section 3.
Anomalies with the resulting CAESAR II geometry can usually be attributed to one of the following causes:
Occasionally an unexpected geometry condition will be handed to the CAESAR II interface program. The solution to this
problem is to update the interface program for the current condition. The user should forward the .UDE file to COADE
for analysis and subsequent interface modification.
An unknown item code was encountered. This indicates that the CADPIPE program has been revised and new item
codes added, which the interface program is unaware of. As before, the interface program will have to be modified to
handle this condition. The user should contact COADE and inform the CAESAR II Technical Support staff of this error
message.
The reassembly of a geometry containing OLETS should be checked carefully. OLET entities in the CADPIPE
connectivity file do not contain a reference to the piping element they intersect. The interface attempts to determine the
associated pipe via coordinate computation and 3D intersection calculations. There is the potential for this procedure to
pass over the intersection point. In this case, the branch containing the OLET will plot at the origin of the CAESAR II
model. This condition can be fixed in the CAESAR II input by breaking the intersected pipe and assigning the OLET
node number to the break point.
8-20 Interfaces
Some CADPIPE connectivity files which have been submitted to COADE for analysis contained errors. These errors
consisted of either pipe doubling back on itself, or piping elements indicated as bends where there was no change in
direction. Both of these errors will be detected by the CAESAR II error checker. However, most users quit before that
stage and conclude that the interface is wrong. Both of these errors should be detected in CADPIPE before the
connectivity file is generated.
ComputerVision Interface
The interface between CAESAR II and ComputerVision is a one way transfer of the geometry data from ComputerVision to
CAESAR II. The geometry data consists of the pipe lengths, diameters, thicknesses, connectivities, and node numbers. All
nodal specific quantities (restraints, loads, displacements, etc.) must be added to the CAESAR II input file in the usual
manner by the user.
The ComputerVision interface is set up so that several models can be transferred in a single session. The first prompt by the
interface is for the name of the ComputerVision neutral file. Once the user specifies this file name, the transfer process
occurs and the interface program prompts for another neutral file name. This is an endless cycle until the user terminates the
session by pressing the Cancel button.
The neutral file read by the interface must be generated by the ComputerVision EXTRACT PIPE module. Details of this
step can be found in the ComputerVision documentation. The ComputerVision neutral file must be transferred into the
CAESAR II directory so that it is available to the interface program.
The interface program reads the ComputerVision neutral file and generates the CAESAR II input file and a log file of the
transfer process. Users should check the data in both the CAESAR II input file and the log file for consistency and any
assumptions made by the interface.
ComputerVision Interface Prompts
Once the ComputerVision interface is started, it prompts the user for the name of the neutral file to be translated. The user
must enter the full file name (prefix, dot, suffix) correctly, or the prompt is repeated. The interface checks for the files
existence and then prompts for an arbitrary coordinate conversion factor. An affirmative response to this query produces a
prompt for the conversion factor. This conversion factor is used to ensure the coordinates are in the same units as the
diameters and thicknesses.
The interface then prompts the user for the location in the neutral file of the tangent intersection points (TIPTs) of the
elbows. Normally, the TIPTs of the bends will be in the section of the neutral file labeled component data. If this is the case,
answer [Y] to the prompt, otherwise answer [N].
Note: The interface will not translate the geometry properly if the TIPTs for some bends are in the component data, while
the TIPTs for other bends are in the grid data.
After these prompts have been answered, the interface translates the ComputerVision neutral file and displays the name of
the generated CAESAR II input file. The interface then prompts for the name of another neutral file for conversion and the
cycle is repeated.
ComputerVision Neutral File
The ComputerVision neutral file is a standard ASCII text file generated by the EXTRACT PIPE module. The data for the
piping system is broken down into distinct sections in the neutral file as outlined below:
General Data. Defines the line name and the units' system used to generate the neutral file. The current CAESAR II units file
should match this units specification, or utilize the arbitrary conversion factor discussed above.
Anchor Data. Defines the coordinates of points described as anchors to the system.
Grid Data. Defines the coordinates of the other nodal points in the system.
Member Data. Describes the element connectivity of the system and references special conditions to the Component Data.
Chapter 8 Interfaces 8-21
Component Data. Defines the coordinates of bend tangent intersection points.
Section Data. Defines the diameter and wall thickness of the various pipe cross sections used in the Member Data.
The other sections of the neutral file are not utilized by the interface program. One assumption made by the interface is that
each of the sections is separated in the file by a blank line. This is important, depending on how the neutral file was
transferred to the CAESAR II directory on the PC. Some communication setups compress out blank lines, which will cause
the interface to abort with an error message.
CAESAR II Log File
The log file generated by the interface contains an image of the data utilized from the neutral file. This data consists of the
Anchor data, the Grid data, the Member data, the Component data, and the Section data. Note that the node numbers are
reassigned, starting with and incrementing by tens. Following the image of the neutral file is the interpreted data, listed in
the standard CAESAR II data matrix format.
Checking the ComputerVision/CAESAR II Data Transfer
It is very important that the resulting CAESAR II input file be verified by the user. The first step in the verification process is
the review of the log file to see if the interpreted data makes sense. The .LOG file is a standard ASCII text file which can be
printed on the system printer or scanned with a text editor. The second step is to enter the input mode of the CAESAR II
program and plot the model. The CAESAR II plot for the ComputerVision example is shown in the following figure.
8-22 Interfaces
Intergraph Interface
This interface transfers a piping system geometry from an Intergraph neutral file into a standard CAESAR II binary input file.
The geometry data consists of the pipe lengths, diameters, thicknesses, connectivities, and node numbers. All nodal specific
quantities (loads, displacements, etc.) must be added to the CAESAR II input file in the usual manner by the user.
There are three basic steps necessary to generate a CAESAR II input file from an Intergraph neutral file:
1 Run the Intergraph PDS Interface module to create an Intergraph neutral file. This ASCII file should then be transferred
to the CAESAR subdirectory.
2 As many Intergraph neutral files as necessary may be created and transferred. The interface will continue to prompt the
user for neutral file names, until the session is terminated by the user by clicking the Cancel button.
3 Ensure the proper units file is active in the directory in which the neutral file is located. This is necessary for the proper
conversion of the data.
Start CAESAR II as usual and enter the TOOLS - EXTERNAL INTERFACES- INTERGRAPH and answer the prompts.
File Name
This is the full path name to the neutral file, which must include the file suffix. On startup, this field is filled with the current
data path. You can manually add a file name to the end of this string, or use the Browse button to search for a neutral file.
Chapter 8 Interfaces 8-23
Browse
This button invokes a standard file selection dialog box from which you can search for the desired neutral file. The top of
this dialog contains controls for switching directories or drives, while the bottom of this dialog contains a control to switch
between the neutral file suffix types (.N or .NEU).
Minimum Anchor Node
This edit box allows the user to change the node number interpreted as the minimum node number for a terminal point in
the model. You should only change the default value if your Intergraph system has been set up with a different anchor node
range.
Maximum Anchor Node
This edit box allows the user to change the node number interpreted as the maximum node number for a terminal point in
the model. You should only change the default value if your Intergraph system has been set up with a different anchor node
range.
Starting Node Number
Allows you to specify the starting node number in the resulting CAESAR II model. The entire model will be renumbered (by
default) using this value as the starting point for the model. To disable renumbering, this value must be set to zero (as well
as the node number increment).
Node Number Increment
Allows you to specify the value used as a node number increment, employed during the renumbering of the model. To
disable renumbering, this value must be set to zero (as well as the starting node number.
Filter Out Elements Whose Diameter is Less Than
This edit box is used to define a minimum allowed pipe size. Any elements less than this minimum diameter will be
ignored. The purpose of this entry is to keep drain lines and taps out of the stress model.
Remove HA Elements
This check box determines whether or not HA elements are removed by this interface. Normally HA (hanger-support
direction) elements should be removed. The support is placed on the pipe where the HA element joints it. Disabling this box
leaves HA elements in the stress model.
Force Consistent Bend Materials
This check box allows the interface to insure that all bend elements (incoming and outgoing) have the same material name
and properties. Often, bends are given a different material name than that of the attached piping, while the properties are the
same. This check box allows the program to change the material information as necessary on the bend elements to that of
the attached piping.
Include Additional Bend Nodes
This check box allows the interface to add a mid-point node and a near-point node on bends.Disabling this box causes bends
to have only the far-point node.
Enable Advanced Element Sort
This check box allows a second, more thorough sorting of the elements. This sort considers the length of the runs, the
diameter, and the elevation in determining where to begin the node numbering sequence. (This option is enabled by default).
Turning this option off employs only the first sort where the elements are sorted starting with the largest (diameter) anchor
nodes and proceeds to the smallest.
8-24 Interfaces
Model Tees as 3 Elements
This option instructs the software to treat tees as 3 elements, instead of condensing them down to a point. In either case, the
SIF is applied at the tee node. Using 3 elements allows pipe properties of the tee to differ from the attached piping.
Model Rotation
This group of radio buttons is used to specify the rotation of the model about the Y axis. The default is zero which leaves
the model alone. The +90 button rotates the model a positive 90 degrees, while the -90 button rotates the model a negative
90 degrees. (Note, the Y axis is vertical in CAESAR II.)
Weight Units
This set of radio buttons enables the software to properly interpret the 'weight' values contained in the neutral file. This is
necessary since the neutral file does not indicate the units for the weight values. The value selected here should match the
corresponding value in the active CAESAR II units file.
Insulation Units
This set of radio buttons enables the software to properly interpret the 'insulation thickness' values contained in the neutral
file. This is necessary since the neutral file does not indicate the units for insulation thickness values. The value selected
here should match the corresponding value in the active CAESAR II units file.
Data Modification and Details
Once the Intergraph interface program returns control to the Main Menu, the CAESAR II binary input files are available for
access. The following modifications and additions will be necessary:
Specification of material properties; Material 1 is assumed, unless a material mapping file is provided. The material
mapping file is discussed below.
Specification of temperatures and pressures; the temperature/pressure pairs are assigned to T1, T2, T3 and P1, and P2 in
order.
Specification of intersection types; unreinforced is assumed.
Specification of restraints details. By default, only anchors and double acting supports are detected by the interface. If
the exact type of restraint is to be transferred, the PDS system must be configured to generate the CAESAR II restraint
type indicators. These restraint type indicators are shown in the "Additional Notes" section of the "complete Neutral
File" interface, discussed later in this chapter. These restraint type values must be placed in field 7 of the first "HA"
property card to be recognized by CAESAR II.
The fluid density can be transferred into CAESAR II also. This density value should be placed in field 7 of the first
PROP card. The density value should be defined according to the density unit used in the CAESAR II units file, not in
terms of specific gravity.
Specification of other loads. The weight of rigid elements can be transferred into CAESAR II for "3W", "4W", "AV",
"RB", and "VA" type elements. In order for the weight of these elements to transfer, the weight value must be placed in
field 8 of the first property card.
Insulation thickness and density can be transferred into CAESAR II also. The thickness and density values should be
placed in fields 9 and 10 of the first PROP card.
In addition, the LOG file generated by the interface should be reviewed for any anomalies. The interface sorts the elements
and then insures that diameters and wall thicknesses are defined for each element. Depending on how disorganized the
Intergraph neutral file is, some assumptions made by the interface may not be correct and therefore require modification of
the resulting CAESAR II input file.
Any major problems encountered by the interface cause the program to abort and no CAESAR II input is generated. Users
experiencing problems of this nature should forward their neutral files to COADE for analysis and subsequent program
modification.
Chapter 8 Interfaces 8-25
If desired, a material mapping file may be defined to relate the material designations in the Intergraph neutral file to the
standard CAESAR II materials. This file must be named "PDS_MAT.MAP" and it must be located beneath the CAESAR II
program directory, in the \SYSTEM subdirectory. This mapping file contains two fields of data per line. Field 1 contains the
PDS material name as it will appear in the neutral file, and is 16 characters wide. Field 2 contains the CAESAR II material
number corresponding to the PDS material name. These values should contain a decimal point, and lie in columns 17 thru
21.
Example Transfer
Listed as follows is an example neutral file from the PDS system.
! Model Design file(s) : ZG2:[006,006]MDLTEST.DGN
! : ZG2:[006,006]EQPTEST.DGN
! Line name(s) : P-1002
! Date : 26-JUL-89 13:58:12
DRAW ,P-1002,P-1002
LOAD, 202000E, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 202000E, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 202000E,3,6,5,3
LOAD, 102001F, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 102001F, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 102001F,3,6,5,3
LOAD, 202000F, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 202000F, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 202000F,3,6,5,3
LOAD, 102001A, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 102001A, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 102001A,3,6,5,3
LOAD, 102001D, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 102001D, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 102001D,3,6,5,3
LOAD, 1020020, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 1020020, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 1020020,3,6,5,3
LOAD, 1020023, 1, 3, 100.00, 300.00, 0.00, 0.00, 300.00, 500.00
LOAD, 1020023, 4, 6, 200.00, 400.00, 0.00, 0.00, 0.00, 0.00
LSET, 1020023,3,6,5,3
CODE,CODE23,ASME2,1982,D
TF, 3020009,16"x10"STDCB390155,,CODE23, 25, 24
PROP,TF, 3020009, 1,A105,0,0,0,0,0,0.
PROP,TF, 3020009, 2,0,0.0,90
8-26 Interfaces
PROP,TF, 3020009, 3,16.,16,BE,0.375,, 202000E
PROP,TF, 3020009, 4,10.,10.75,BE,0.365,, 102001F
RB, 302000B,16"STDCB30255,,CODE23, 901, 26
PROP,RB, 302000B, 1,A234-WPB,0,0,0,0,0,0.
PROP,RB, 302000B, 3,16.,16,BW,0.375,, 202000E
PROP,RB, 302000B, 4,0.,0,BW,0.,, 202000E
PI, 5020013,16"STDCB10075,,CODE23, 26, 25
PROP,PI, 5020013, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020013, 3,16.,16,BW,0.375,, 202000E
PROP,PI, 5020013, 4,16.,16,BW,0.375,, 202000E
RB, 302000A,16"STDCB30255,,CODE23, 902, 12
PROP,RB, 302000A, 1,A234-WPB,0,0,0,0,0,0.
PROP,RB, 302000A, 3,16.,16,BW,0.375,, 202000F
PROP,RB, 302000A, 4,0.,0,BW,0.,, 202000F
TF, 302000C,16"x10"STDCB390155,,CODE23, 15, 14
PROP,TF, 302000C, 1,A105,0,0,0,0,0,0.
PROP,TF, 302000C, 2,0,0.0,90
PROP,TF, 302000C, 3,16.,16,BE,0.375,, 202000F
PROP,TF, 302000C, 4,10.,10.75,BE,0.365,, 102001A
PI, 5020014,16"STDCB10075,,CODE23, 17, 15
PROP,PI, 5020014, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020014, 3,16.,16,BW,0.375,, 102001D
PROP,PI, 5020014, 4,16.,16,BW,0.375,, 102001D
FL, 3020042,10"STDCB20015,,CODE23, 27, 13
PROP,FL, 3020042, 1,A105,0,0,0,0,0,0.
PROP,FL, 3020042, 3,10.,16,WN,0.,CL150, 102001A
PROP,FL, 3020042, 4,10.,10.75,BW,0.365,CL150, 102001A
PI, 5020015,10"STDCB10075,,CODE23, 14, 13
PROP,PI, 5020015, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020015, 3,10.,10.75,BW,0.365,, 102001A
PROP,PI, 5020015, 4,10.,10.75,BW,0.365,, 102001A
TE, 3020008,16"STDCB30245,,CODE23, 22, 17, 20, 951
PROP,TE, 3020008, 1,A234-WPB,0,0,0,0,0,0.
PROP,TE, 3020008, 2,0,0.0,90
PROP,TE, 3020008, 3,16.,16,BW,0.375,, 1020020
PROP,TE, 3020008, 4,16.,16,BW,0.375,, 102001D
PROP,TE, 3020008, 5,16.,16,BW,0.375,, 1020023
FL, 3020041,10"STDCB20015,,CODE23, 28, 23
Chapter 8 Interfaces 8-27
PROP,FL, 3020041, 1,A105,0,0,0,0,0,0.
PROP,FL, 3020041, 3,10.,16,WN,0.,CL150, 102001F
PROP,FL, 3020041, 4,10.,10.75,BW,0.365,CL150, 102001F
PI, 5020012,10"STDCB10075,,CODE23, 23, 24
PROP,PI, 5020012, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020012, 3,10.,10.75,BW,0.365,, 102001F
PROP,PI, 5020012, 4,10.,10.75,BW,0.365,, 102001F
EL, 3020040,16"STDCB30215,,CODE23, 903, 1, 952
PROP,EL, 3020040, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 3020040, 2,24,90,0,0.
PROP,EL, 3020040, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 3020040, 4,16.,16,BW,0.375,, 1020023
EL, 3020023,16"STDCB30215,,CODE23, 18, 16, 953
PROP,EL, 3020023, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 3020023, 2,24,90,0,0.
PROP,EL, 3020023, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 3020023, 4,16.,16,BW,0.375,, 1020023
EL, 3020024,16"STDCB30215,,CODE23, 16, 10, 954
PROP,EL, 3020024, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 3020024, 2,24,90,0,0.
PROP,EL, 3020024, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 3020024, 4,16.,16,BW,0.375,, 1020023
EL, 302002A,16"STDCB30215,,CODE23, 11, 9, 955
PROP,EL, 302002A, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302002A, 2,24,90,0,0.
PROP,EL, 302002A, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 302002A, 4,16.,16,BW,0.375,, 1020023
EL, 302002B,16"STDCB30215,,CODE23, 8, 6, 956
PROP,EL, 302002B, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302002B, 2,24,90,0,0.
PROP,EL, 302002B, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 302002B, 4,16.,16,BW,0.375,, 1020023
EL, 302003C,16"STDCB30235,,CODE23, 5, 3, 957
PROP,EL, 302003C, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302003C, 2,24.1421,45,0,0.
PROP,EL, 302003C, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 302003C, 4,16.,16,BW,0.375,, 1020023
8-28 Interfaces
EL, 302003D,16"STDCB30215,,CODE23, 4, 2, 958
PROP,EL, 302003D, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302003D, 2,24,90,0,0.
PROP,EL, 302003D, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 302003D, 4,16.,16,BW,0.375,, 1020023
PI, 5020016,16"STDCB10075,,CODE23, 19, 18
PROP,PI, 5020016, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020016, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 5020016, 4,16.,16,BW,0.375,, 1020023
PI, 5020018,16"STDCB10075,,CODE23, 10, 11
PROP,PI, 5020018, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020018, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 5020018, 4,16.,16,BW,0.375,, 1020023
PI, 5020019,16"STDCB10075,,CODE23, 9, 8
PROP,PI, 5020019, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5020019, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 5020019, 4,16.,16,BW,0.375,, 1020023
PI, 502001A,16"STDCB10075,,CODE23, 6, 7
PROP,PI, 502001A, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 502001A, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 502001A, 4,16.,16,BW,0.375,, 1020023
PI, 502001B,16"STDCB10075,,CODE23, 3, 4
PROP,PI, 502001B, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 502001B, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 502001B, 4,16.,16,BW,0.375,, 1020023
PI, 502001C,16"STDCB10075,,CODE23, 2, 1
PROP,PI, 502001C, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 502001C, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 502001C, 4,16.,16,BW,0.375,, 1020023
EL, 302003E,16"STDCB30235,,CODE23, 5, 7, 959
PROP,EL, 302003E, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302003E, 2,24.1421,45,0,0.
PROP,EL, 302003E, 3,16.,16,BW,0.375,, 1020023
PROP,EL, 302003E, 4,16.,16,BW,0.375,, 1020023
EL, 302005A,16"STDCB30215,,CODE23, 19, 21, 960
PROP,EL, 302005A, 1,A234-WPB,0,0,0,0,0,0.
PROP,EL, 302005A, 2,24,90,0,0.
PROP,EL, 302005A, 3,16.,16,BW,0.375,, 1020023
Chapter 8 Interfaces 8-29
PROP,EL, 302005A, 4,16.,16,BW,0.375,, 1020023
PI, 502005E,16"STDCB10075,,CODE23, 21, 20
PROP,PI, 502005E, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 502005E, 3,16.,16,BW,0.375,, 1020023
PROP,PI, 502005E, 4,16.,16,BW,0.375,, 1020023
PI, 5027531,16"STDCB10075,,CODE23, 25, 22
PROP,PI, 5027531, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5027531, 3,16.,16,BW,0.375,, 1020020
PROP,PI, 5027531, 4,16.,16,BW,0.375,, 1020020
PI, 5027532,16"STDCB10075,,CODE23, 15, 12
PROP,PI, 5027532, 1,API-5L-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00
PROP,PI, 5027532, 3,16.,16,BW,0.375,, 202000F
PROP,PI, 5027532, 4,16.,16,BW,0.375,, 202000F
LNOD, 27,RE, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0
LNOD, 28,RE, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0
NODE, 1, 12024.00, 12000.00, 3011.12, 2, 0.00
NODE, 2, 12044.50, 12000.00, 3011.12, 2, 0.00
NODE, 3, 12068.50, 12000.00, 2470.00, 2, 0.00
NODE, 4, 12068.50, 12000.00, 2987.12, 2, 0.00
NODE, 5, 12075.57, 12000.00, 2452.93, 2, 0.00
NODE, 6, 12082.64, 12000.00, 1764.00, 2, 0.00
NODE, 7, 12082.64, 12000.00, 2435.86, 2, 0.00
NODE, 8, 12106.64, 12000.00, 1740.00, 2, 0.00
NODE, 9, 12168.00, 12000.00, 1740.00, 2, 0.00
NODE, 10, 12192.00, 11815.00, 1740.00, 2, 0.00
NODE, 11, 12192.00, 11976.00, 1740.00, 2, 0.00
NODE, 12, 12198.00, 11911.00, 1644.00, 2, 0.00
NODE, 13, 12210.00, 11911.00, 1594.12, 2, 0.00
NODE, 14, 12210.00, 11911.00, 1632.94, 2, 0.00
NODE, 15, 12210.00, 11911.00, 1644.00, 2, 0.00
NODE, 16, 12216.00, 11791.00, 1740.00, 2, 0.00
NODE, 17, 12228.00, 11911.00, 1644.00, 2, 0.00
NODE, 18, 12240.00, 11815.00, 1740.00, 2, 0.00
NODE, 19, 12240.00, 11887.00, 1740.00, 2, 0.00
NODE, 20, 12240.00, 11911.00, 1656.00, 2, 0.00
NODE, 21, 12240.00, 11911.00, 1716.00, 2, 0.00
NODE, 22, 12252.00, 11911.00, 1644.00, 2, 0.00
8-30 Interfaces
NODE, 23, 12270.00, 11911.00, 1594.12, 2, 0.00
NODE, 24, 12270.00, 11911.00, 1632.94, 2, 0.00
NODE, 25, 12270.00, 11911.00, 1644.00, 2, 0.00
NODE, 26, 12282.00, 11911.00, 1644.00, 2, 0.00
NODE, 27, 12210.00, 11911.00, 1590.05, 2, 0.00
NODE, 28, 12270.00, 11911.00, 1590.05, 2, 0.00
NODE, 901, 12285.50, 11911.00, 1644.00, 2, 0.00
NODE, 902, 12194.50, 11911.00, 1644.00, 2, 0.00
NODE, 903, 12000.00, 12000.00, 2987.12, 2, 0.00
NODE, 904, 12210.00, 11911.00, 1577.18, 2, 0.00
NODE, 905, 12270.00, 11911.00, 1577.18, 2, 0.00
NODE, 951, 12240.00, 11911.00, 1644.00, 2, 0.00
NODE, 952, 12000.00, 12000.00, 3011.12, 2, 0.00
NODE, 953, 12240.00, 11791.00, 1740.00, 2, 0.00
NODE, 954, 12192.00, 11791.00, 1740.00, 2, 0.00
NODE, 955, 12192.00, 12000.00, 1740.00, 2, 0.00
NODE, 956, 12082.64, 12000.00, 1740.00, 2, 0.00
NODE, 957, 12068.50, 12000.00, 2460.00, 2, 0.00
NODE, 958, 12068.50, 12000.00, 3011.12, 2, 0.00
NODE, 959, 12082.64, 12000.00, 2445.86, 2, 0.00
NODE, 960, 12240.00, 11911.00, 1740.00, 2, 0.00
Chapter 8 Interfaces 8-31
The .LOG file produced by the CAESAR II translator is shown below, followed by a plot of the job from the CAESAR II input
module.
*** CAESAR II / Intergraph Geometry Translator ***
INTERGRAPH DATA AS READ IN FOR FILE: P-1002.NEU
Maximum Temperature and Pressure encountered: 300.0 500.0
Looking for node: 901
Have sorted element: 1, its location pointer is: 2
Number of resume nodes is: 0
Element type is: 10
Looking for node: 26
Have sorted element: 2, its location pointer is: 3
Number of resume nodes is: 0
Element type is: 9
Looking for node: 25
Have sorted element: 3, its location pointer is: 1
Number of resume nodes is: 0
Element type is: 14
Looking for node: 24
Have sorted element: 4, its location pointer is: 11
Number of resume nodes is: 0
Element type is: 9
Looking for node: 23
Have sorted element: 5, its location pointer is: 10
Number of resume nodes is: 0
Element type is: 7
Looking for node: 28
Looking for node: 902
Have sorted element: 6, its location pointer is: 4
8-32 Interfaces
Number of resume nodes is: 0
Element type is: 10
Looking for node: 12
Have sorted element: 7, its location pointer is: 29
Number of resume nodes is: 0
Element type is: 9
Looking for node: 15
Have sorted element: 8, its location pointer is: 5
Number of resume nodes is: 0
Element type is: 14
Looking for node: 14
Have sorted element: 9, its location pointer is: 8
Number of resume nodes is: 0
Element type is: 9
Looking for node: 13
Have sorted element: 10, its location pointer is: 7
Number of resume nodes is: 0
Element type is: 7
Looking for node: 27
Looking for node: 903
Have sorted element: 11, its location pointer is: 12
Number of resume nodes is: 0
Element type is: 5
Looking for node: 1
Have sorted element: 12, its location pointer is: 24
Number of resume nodes is: 0
Element type is: 9
Looking for node: 2
Have sorted element: 13, its location pointer is: 18
Number of resume nodes is: 0
Element type is: 5
Looking for node: 4
Chapter 8 Interfaces 8-33
Have sorted element: 14, its location pointer is: 23
Number of resume nodes is: 0
Element type is: 9
Looking for node: 3
Have sorted element: 15, its location pointer is: 17
Number of resume nodes is: 0
Element type is: 5
Looking for node: 5
Have sorted element: 16, its location pointer is: 25
Number of resume nodes is: 0
Element type is: 5
Looking for node: 7
Have sorted element: 17, its location pointer is: 22
Number of resume nodes is: 0
Element type is: 9
Looking for node: 6
Have sorted element: 18, its location pointer is: 16
Number of resume nodes is: 0
Element type is: 5
Looking for node: 8
Have sorted element: 19, its location pointer is: 21
Number of resume nodes is: 0
Element type is: 9
Looking for node: 9
Have sorted element: 20, its location pointer is: 15
Number of resume nodes is: 0
Element type is: 5
Looking for node: 11
Have sorted element: 21, its location pointer is: 20
Number of resume nodes is: 0
8-34 Interfaces
Element type is: 9
Looking for node: 10
Have sorted element: 22, its location pointer is: 14
Number of resume nodes is: 0
Element type is: 5
Looking for node: 16
Have sorted element: 23, its location pointer is: 13
Number of resume nodes is: 0
Element type is: 5
Looking for node: 18
Have sorted element: 24, its location pointer is: 19
Number of resume nodes is: 0
Element type is: 9
Looking for node: 19
Have sorted element: 25, its location pointer is: 26
Number of resume nodes is: 0
Element type is: 5
Looking for node: 21
Have sorted element: 26, its location pointer is: 27
Number of resume nodes is: 0
Element type is: 9
Looking for node: 20
Have sorted element: 27, its location pointer is: 9
Number of resume nodes is: 0
Element type is: 13
Looking for node: 22
Have sorted element: 28, its location pointer is: 28
Number of resume nodes is: 1
Element type is: 9
Looking for node: 25
Chapter 8 Interfaces 8-35
Looking for node: 17
Have sorted element: 29, its location pointer is: 6
Number of resume nodes is: 0
Element type is: 9
Looking for node: 15
Intergraph Data After Element Sort
8-36 Interfaces
Intergraph Data After TEE/Cross Modifications
(End nodes replaced with center point, and TEE/CROSS element removed. Modifications also performed on 3 & 4 way
valves.)
Chapter 8 Interfaces 8-37
Intergraph Data After Valve Modifications
(Flange lengths added to valve lengths.)
** BEND MODIFICATION START **
INCOMING ELEMENT: 11 NODES: 1 903
BEND ELEMENT : 11 NODES: 903 1
EXITING ELEMENT : 12 NODES: 1 2
CURRENT COORDINTES FOR ELEMENT: 11
NODE: 1 X, Y, Z = 12024.00 3011.12 -12000.00
NODE: 903 X, Y, Z = 12000.00 2987.12 -12000.00
8-38 Interfaces
CURRENT COORDINTES FOR ELEMENT: 12
NODE: 1 X, Y, Z = 12024.00 3011.12 -12000.00
NODE: 2 X, Y, Z = 12044.50 3011.12 -12000.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 1 X, Y, Z = 12000.00 3011.12 -12000.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 13 NODES: 4 2
BEND ELEMENT : 13 NODES: 2 4
EXITING ELEMENT : 14 NODES: 4 3
CURRENT COORDINTES FOR ELEMENT: 13
NODE: 4 X, Y, Z = 12068.50 2987.12 -12000.00
NODE: 2 X, Y, Z = 12044.50 3011.12 -12000.00
CURRENT COORDINTES FOR ELEMENT: 14
NODE: 4 X, Y, Z = 12068.50 2987.12 -12000.00
NODE: 3 X, Y, Z = 12068.50 2470.00 -12000.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 4 X, Y, Z = 12068.50 3011.12 -12000.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 15 NODES: 5 3
BEND ELEMENT : 15 NODES: 3 5
EXITING ELEMENT : 16 NODES: 5 7
Chapter 8 Interfaces 8-39
CURRENT COORDINTES FOR ELEMENT: 15
NODE: 5 X, Y, Z = 12075.57 2452.93 -12000.00
NODE: 3 X, Y, Z = 12068.50 2470.00 -12000.00
CURRENT COORDINTES FOR ELEMENT: 16
NODE: 5 X, Y, Z = 12075.57 2452.93 -12000.00
NODE: 7 X, Y, Z = 12082.64 2435.86 -12000.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 5 X, Y, Z = 12068.50 2460.00 -12000.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 16 NODES: 7 5
BEND ELEMENT : 16 NODES: 5 7
EXITING ELEMENT : 17 NODES: 7 6
CURRENT COORDINTES FOR ELEMENT: 16
NODE: 7 X, Y, Z = 12082.64 2435.86 -12000.00
NODE: 5 X, Y, Z = 12068.50 2460.00 -12000.00
CURRENT COORDINTES FOR ELEMENT: 17
NODE: 7 X, Y, Z = 12082.64 2435.86 -12000.00
NODE: 6 X, Y, Z = 12082.64 1764.00 -12000.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 7 X, Y, Z = 12082.64 2445.86 -12000.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 18 NODES: 8 6
BEND ELEMENT : 18 NODES: 6 8
EXITING ELEMENT : 19 NODES: 8 9
8-40 Interfaces
CURRENT COORDINTES FOR ELEMENT: 18
NODE: 8 X, Y, Z = 12106.64 1740.00 -12000.00
NODE: 6 X, Y, Z = 12082.64 1764.00 -12000.00
CURRENT COORDINTES FOR ELEMENT: 19
NODE: 8 X, Y, Z = 12106.64 1740.00 -12000.00
NODE: 9 X, Y, Z = 12168.00 1740.00 -12000.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 8 X, Y, Z = 12082.64 1740.00 -12000.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 20 NODES: 11 9
BEND ELEMENT : 20 NODES: 9 11
EXITING ELEMENT : 21 NODES: 11 10
CURRENT COORDINTES FOR ELEMENT: 20
NODE: 11 X, Y, Z = 12192.00 1740.00 -11976.00
NODE: 9 X, Y, Z = 12168.00 1740.00 -12000.00
CURRENT COORDINTES FOR ELEMENT: 21
NODE: 11 X, Y, Z = 12192.00 1740.00 -11976.00
NODE: 10 X, Y, Z = 12192.00 1740.00 -11815.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 11 X, Y, Z = 12192.00 1740.00 -12000.00
Chapter 8 Interfaces 8-41
** BEND MODIFICATION START **
INCOMING ELEMENT: 22 NODES: 16 10
BEND ELEMENT : 22 NODES: 10 16
EXITING ELEMENT : 23 NODES: 16 18
CURRENT COORDINTES FOR ELEMENT: 22
NODE: 16 X, Y, Z = 12216.00 1740.00 -11791.00
NODE: 10 X, Y, Z = 12192.00 1740.00 -11815.00
CURRENT COORDINTES FOR ELEMENT: 23
NODE: 16 X, Y, Z = 12216.00 1740.00 -11791.00
NODE: 18 X, Y, Z = 12240.00 1740.00 -11815.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 16 X, Y, Z = 12192.00 1740.00 -11791.00
** BEND MODIFICATION START **
INCOMING ELEMENT: 23 NODES: 18 16
BEND ELEMENT : 23 NODES: 16 18
EXITING ELEMENT : 24 NODES: 18 19
CURRENT COORDINATES FOR ELEMENT: 23
NODE: 18 X, Y, Z = 12240.00 1740.00 -11815.00
NODE: 16 X, Y, Z = 12192.00 1740.00 -11791.00
CURRENT COORDINTES FOR ELEMENT: 24
NODE: 18 X, Y, Z = 12240.00 1740.00 -11815.00
NODE: 19 X, Y, Z = 12240.00 1740.00 -11887.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 18 X, Y, Z = 12240.00 1740.00 -11791.00
8-42 Interfaces
** BEND MODIFICATION START **
INCOMING ELEMENT: 25 NODES: 21 19
BEND ELEMENT : 25 NODES: 19 21
EXITING ELEMENT : 26 NODES: 21 951
CURRENT COORDINTES FOR ELEMENT: 25
NODE: 21 X, Y, Z = 12240.00 1716.00 -11911.00
NODE: 19 X, Y, Z = 12240.00 1740.00 -11887.00
CURRENT COORDINTES FOR ELEMENT: 26
NODE: 21 X, Y, Z = 12240.00 1716.00 -11911.00
NODE: 951 X, Y, Z = 12240.00 1644.00 -11911.00
COMPUTED TANGENT INTERSECTION POINT
NODE: 21 X, Y, Z = 12240.00 1740.00 -11911.00
Chapter 8 Interfaces 8-43
Intergraph Data After Bend Modifications
8-44 Interfaces
(Far Weld Line Nodal coordinates changed to Tangent Intersection Point coordinates)
DATA FOR PROPERTY ARRAY WITH # ENTRIES = 5
LOCATIONS 1-11
LOCATIONS 1, 12-20
Chapter 8 Interfaces 8-45
*** CAESAR II INTERPRETED GEOMETRY DATA ***
*** CAESAR II INTERPRETED PROPERTY DATA *** Part 1
*** CAESAR II INTERPRETED PROPERTY DATA *** Part 2
8-46 Interfaces
Chapter 8 Interfaces 8-47
8-48 Interfaces
The CAESAR II job file name is P-1002_A Y
Starting generation of CAESAR II input file for:
28 elements
9 Bends
2 Rigids
2 Restraints
Conversion of data to CAESAR II completed
Chapter 8 Interfaces 8-49
PRO-ISO Interface
The interface between CAESAR II and PRO-ISO is a one way transfer of the geometry data from PRO-ISO to CAESAR II.
The geometry data consists of the pipe lengths, diameters, thicknesses, connectivities, and node numbers. All nodal specific
quantities (restraints, loads, displacements, etc.) must be added to the CAESAR II input file in the usual manner by the user.
Select the PRO-ISO option from the TOOLS/EXTERNAL INTERFACES menu and enter the name of the PRO-ISO neutral file. Once
the user specifies the name of the file (without an extension), the transfer process occurs and the interface program prompts
for another neutral file name. This is an endless cycle until the user presses the Cancel button. The neutral files generated
by the interface will have the suffixes .PI1 and .PI2.
The neutral files read by the interface program must be generated by the PRO-ISO program. Details of this step can be
found in the PRO-ISO documentation. The PRO-ISO neutral files must be transferred into the CAESAR II directory so that
they are available to the interface program.
The interface program reads the PRO-ISO neutral files and generates the CAESAR II input file and a log file of the transfer
process. Users should check the data in both the CAESAR II input file and the log file for consistency and any assumptions
made by the interface. The data transferred (and the data structure) is described below.
In the first file, a record is required for each piece of pipe in the system. A pipe in this sense is an entity between two
nodes, which could be a pipe, or a rigid element. There are 12 values per entry, where all values must be specified.
Field 1 - ELMT
This is the pipe element number, which may correspond to an entry in the second file. This is also the pipe/element number
in the model. These values should be sequential from 1.
8-50 Interfaces
Field 2 - N1
This is the FROM node number, i.e. the starting node for the element. These values must be greater than zero and less
than 32000.
Field 3 - N2
This is the TO node number, i.e. the ending node for the element. These values must be greater than zero and less than
32000.
Field 4 - DX
This is the delta X dimension for the element. This is the distance between N1 and N2 in the X direction.
Field 5 - DY
This is the delta Y dimension for the element. This is the distance between N1 and N2 in the Y direction. In CAESAR II,
Y is vertical.
Field 6 - DZ
This is the delta Z dimension for the element. This is the distance between N1 and N2 in the Z direction.
Field 7 - DIAM
This is the pipe outer diameter.
Field 8 - THK
This is the pipe wall thickness.
Field 9 - ANCH
This is a restraint (support) indicator flag. If ANCH is 1, then there is a restraint on N1. If ANCH is 2, then there is a
restraint on N2. The type of restraint can be obtained from the second file.
Field 10 - BND
This field indicates the presence of a bend at the N2 end of the element. If BND is 1, there is a bend at N2. If BND is 0, this
is a straight pipe.
Field 11 - BRAD
This field is used to specify the bend radius if the bend is not a long radius bend. The value here should be the desired bend
radius.
Field 12 - RIGD
This field is a flag used to indicate that the current element is a rigid element. The weight of the element can be obtained
from the second file.
Records in the second file are only necessary when additional data is required. This means there will always be a record in
the second file for pipe element #1 (this could be the only entry in the file). Any additional entries will contain some type of
change to data normally duplicated forward by CAESAR II.
Chapter 8 Interfaces 8-51
Field 1 - ELMT
This is the pipe element number, which corresponds to an entry in the first file. This is also a pipe/element number in the
model. These numbers are sequential from 1.
Field 2 - TEMP1
This is the operating temperature for load case 1, found by scanning the PRO-ISO data for the maximum temperature.
Field 3 - PRESS1
This is the operating pressure for load case 1, found by scanning the PRO-ISO data for the maximum pressure.
Field 4 - RGDWGT
This value is the weight of rigid elements. This entry is only required if the RIGID flag was set in the first file.
Field 5 - TEEFLG
This value indicates the TEE type.
1 - reinforced
2 - unreinforced
3 - welding tee
4 - sweepolet
5 - weldolet
6 - extruded welding tee
Field 6 - RESTYP
This value is the restraint (support) type indicator. Type values are:
0 - anchor
1 - double acting X
2 - double acting Y
3 - double acting Z
4 - double acting RX
5 - double acting RY
6 - double acting RZ
8-52 Interfaces
Field 7 - RINFO1
Data for supports, by default, the restraint stiffness.
Field 8 - RINFO2
Data for supports, by default, the restraint gap.
Field 9 - RINFO3
Data for supports, by default, the restraint friction coefficient.
Field 10 - MATID
The CAESAR II material ID value. Note that if the coefficient of expansion is to be changed, it should be entered in the
Temperature field above (Field 2).
Field 11 - EMOD
The value of Youngs modulus.
Field 12 - POIS
The value of Poissons ratio.
Field 13 - GAMMA
The weight density of the material.
Field 14 - INSTHK
The insulation thickness.
Field 15 - INSWGT
The weight density of the insulation material.
Field 16 - FLDWGT
The weight density of the pipe contents (fluid).
Field 17 - TEENOD
The element node number where there is a tee.
Field 18 - (Placeholder for future development.)
Field 19 - (Placeholder for future development.)
Field 20 - (Placeholder for future development.)
Chapter 8 Interfaces 8-53
PRO-ISO Example Transfer
Listed below are example neutral files produced by the PRO-ISO program. Note that the field width for each value is
actually 13 characters. The figures below have been compressed for this documentation.
As the interface runs, status messages are displayed on the users terminal for informative purposes. Once the transfer is
complete, the user should review the .LOG file generated to insure that there are no unexplained errors or warnings. The
.LOG file generated for the above neutral files is listed next.
*** CAESAR II / ADEV Geometry Translator ***
ADEV data as read in for GEOMETRY file: TEST1.PI1
PROPERTY file: TEST1.PI2
Starting read of CAD neutral files.
CAD geometry successfully read.
CAD properties successfully read.
8-54 Interfaces
*** C A E S A R I I INTERPRETED GEOMETRY DATA ***
*** C A E S A R II INTERPRETED PROPERTY DATA *** Part 1
*** C A E S A R II INTERPRETED PROPERTY DATA *** Part 2
Data transferred to CAESAR II array structures.
The CAESAR II job file name is: TEST1._A
Starting generation of CAESAR II input file for:
15 Elements
2 Bends
1 Rigids
5 Restraints
Conversion of data to CAESAR II completed.
Chapter 8 Interfaces 8-55
Checking the PRO-ISO/CAESAR II Data Transfer
It is very important that the resulting CAESAR II input file be verified by the user. The first step in the verification process is
the review of the log file to see if any errors or warnings were generated. (The .LOG file is a standard ASCII text file which
can be printed on the system printer or scanned with a text editor.) The second step is to enter the input mode of the
CAESAR II program and plot the model. The CAESAR II plot for the above example is shown in the following figure.
PCF Interface
The PCF file format is a standard drawing exchange format developed by Alias Ltd. The PCF file is a flat text file,
containing detailed information about the piping system components, as extracted from a CAD system. The CAESAR II PCF
interface can read in a PCF file, and generate a CAESAR II input file from the acquired information.
Details on the format of the PCF file, and its capabilities can be obtained from Alias. To invoke the PCF Interface select
TOOLS/PCF from the CAESAR II Main Menu. A dialog box like the one below will appear. Explanations of each field are
provided following the figure.
8-56 Interfaces
File Name
This is the full path name to the neutral file, which must include the file suffix. On startup, this field is filled with the current
data path. You can manually add a file name to the end of this string, or use the Browse button to search for a neutral file.
Browse
Invokes a standard file selection dialog box from which you can search for the desired neutral file. The top of this dialog
contains controls for switching directories or drives, while the bottom of this dialog contains a control to switch between the
neutral file suffix types (.N or .NEU).
Starting Node Number
Allows you to specify the starting node number in the resulting CAESAR II model. The entire model will be renumbered (by
default) using this value as the starting point for the model. To disable renumbering, this value must be set to zero (as well
as the node number increment).
Node Number Increment
Allows you to specify the value used as a node number increment, employed during the renumbering of the model. To
disable renumbering, this value must be set to zero (as well as the starting node number.
Condense Tees
This option instructs the software NOT to treat tees as 3 elements, condensing them down to a point. In either case, the SIF
is applied at the tee node. Using 3 elements allows pipe properties of the tee to differ from the attached piping.
Condense Elbows
This option instructs the software NOT to treat elbows as 2 elements, one element for each direction the elbow travels in.
Condense Connected Rigids
This option instructs the software to combine rigids that connect to each other into a single element.
Assume Standard Schedule
This option instructs the software to compute, wall thicknesses based on the diameter of the pipe and standard schedule.
Without this option, no wall thickness will be specified (for the JIS pipe specification, this option assumes Sch 40).
Model Rotation
This group of radio buttons is used to specify the rotation of the model about the Y axis. The default is zero which leaves
the model alone. The +90 button rotates the model a positive 90 degrees, while the -90 button rotates the model a negative
90 degrees. (Note, the Y axis is vertical in CAESAR II.)
Chapter 8 Interfaces 8-57
Generic Neutral Files
CAESAR II Neutral File Interface
The general neutral file can be used to send data either in to or out of the standard CAESAR II binary input file, otherwise
known as the _A file. The name of the file used or generated by this interface is the CAESAR II jobname with the extension
.CII. The intent of this interface is to allow users access to any particular data item from a _A input file, to enable a
complete _A file to be built from a CAD program, and to allow CAESAR II input data to be used for other analysis purposes.
Users implementing this interface should be warned that the content and format described in this section is subject to
change, as a function of the enhancements made to the CAESAR II program. Every effort will be made to keep such drastic
changes to a minimum.
Several third-party CAD programs, such as AVEVAs PDMS and Jacobus Plant Space also support this neutral file. If
desired, instead of invoking this interface from the "Tools\External Interface" menu, this processor can be run in "batch
mode", from either a batch file or the command line. This batch command takes the form:
f:\ProgramDirectory\iecho f:\DataDirectory\NeutralFile.cii
where "f:\ProgramDirectory" and "f:\DataDirectory" should be changed appropriately.
The CAESAR II neutral file, henceforth referred to as the .CII file, is divided into sections which organize the piping data in
logical groupings. Each major section is discussed below. Details of each item are discussed to the right of the page. Section
divisions are denoted in the neutral file by the #$ character sequence found in columns 1 & 2. The token following the
#$ character sequence is a section identifier, used by the program for data sequencing purposes, and to aid the user in
reading the neutral file.
For each item listed on the following pages, the necessary FORTRAN format for the input/output is provided. The
following variables are used in dimensioning arrays:
N1Base memory allocation quantity, used to set array sizes. For example, if N1=2,000, your neutral file can handle
up to 2,000 elements.
N21/2 N1
N31/3 N1
N41/4 N1
N51/5 N1
N6N1/13.33
Version and Job Title Information
#$ VERSION. This is the section division header. The #$ and space are required, as well as the word VERSION, all in
capital letters.
Use FORTRAN format (2X, 4G13.6) to write the values of the following variables on the first line of the neutral file:
GVERSION is the version of the neutral file interface being used. This corresponds to the major version number of
CAESAR II, i.e. 4 for 4.x.
RVERSION is the specific CAESAR II version generating this file, i.e. 4.50.
SPARE are unused (at this time) locations on the record.
The next 60 lines of 75 characters each are reserved for the CAESAR II title-page text. Use FORTRAN format (2X, A75).
The last line of the job title array, if found to be blank, is set by this transfer program. The text that is set here indicates that
the file was created by this interface.
8-58 Interfaces
Control Information
#$ CONTROL. This is the section division header. The #$ and space are required, as well as the word CONTROL, in
capital letters.
Use FORTRAN format (2X, 4I13) to write the values of the following variables on the next line of the neutral file:
NUMELT is the number of piping elements (spreadsheets) in the input file.
NUMNOZ is the number of nozzles in the input file.
NOHGRS is the number of spring hangers in the input file.
NONAM is the number of Node Name data blocks in the input file.
NORED is the number of reducers in the input file.
NUMFLG is the number of flanges in the input file.
Next, write 11-members of the array (IAUXAU) that contains the number of auxiliary data types used in the input file,
followed by the vertical axis indicator. Use FORTRAN format (2X, 6I13).
These 11 values from the IAUXAU array are the following:
1 The number of bend auxiliary data blocks in the input file.
2 The number of rigid-element auxiliary data blocks in the input file.
3 The number of expansion-joint auxiliary data blocks in the input file.
4 The number of restraint auxiliary data blocks in the input file.
5 The number of displacement auxiliary data blocks in the input file.
6 The number of force/moment auxiliary data blocks in the input file.
7 The number of uniform-load auxiliary data blocks in the input file.
8 The number of wind-load auxiliary data blocks in the input file.
9 The number of element-offset auxiliary data blocks in the input file.
10 The number of allowable-stress auxiliary data blocks in the input file.
11 The number of intersection auxiliary data blocks in the input file.
IZUP flag. Equal to 0 for the global -Y axis vertical, equal to 1 for the global -Z axis vertical.
Basic Element Data
#$ ELEMENTS. This is the section division header. The #$ and space are required, as well as the word ELEMENTS, all
in capital letters.
This section of the file contains integer and real data for each element in the input file. The data are organized as such:
1 real values for element i
2 integer values for element i
3 real values for element i+1
4 integer values for element i+1
These real and integer values are stored in arrays, described as follows:
A 50-member array (REL) contains the real basic-element data. The REL array is dimensioned (N1,50).
Use FORTRAN format (2X, 6G13.6) to write the values of the following 45 items on the appropriate eight lines of the
neutral file.
Chapter 8 Interfaces 8-59
1 FROM node number
2 TO node number
3 Delta X
4 Delta Y
5 Delta Z
6 Diameter (value stored here is actual OD)
7 Wall Thickness (actual)
8 Insulation Thickness
9 Corrosion Allowance
10 Thermal Expansion Coefficient #1 (or Temperature #1)
11 Thermal Expansion Coefficient #2 (or Temperature #2)
12 Thermal Expansion Coefficient #3 (or Temperature #3)
13 Thermal Expansion Coefficient #4 (or Temperature #4)
14 Thermal Expansion Coefficient #5 (or Temperature #5)
15 Thermal Expansion Coefficient #6 (or Temperature #6)
16 Thermal Expansion Coefficient #7 (or Temperature #7)
17 Thermal Expansion Coefficient #8 (or Temperature #8)
18 Thermal Expansion Coefficient #9 (or Temperature #9)
19 Pressure #1
20 Pressure #2
21 Pressure #3
22 Pressure #4
23 Pressure #5
24 Pressure #6
25 Pressure #7
26 Pressure #8
27 Pressure #9
28 Elastic Modulus (cold)
29 Poissons Ratio
30 Pipe Density
31 Insulation Density
32 Fluid Density
33 Minus Mill Tolerance
34 Plus Mill Tolerance
35 Seam Weld (1=Yes, 0=No)
36 Hydro Pressure
37 Elastic Modulus (Hot #1)
8-60 Interfaces
38 Elastic Modulus (Hot #2)
39 Elastic Modulus (Hot #3)
40 Elastic Modulus (Hot #4)
41 Elastic Modulus (Hot #5)
42 Elastic Modulus (Hot #6)
43 Elastic Modulus (Hot #7)
44 Elastic Modulus (Hot #8)
45 Elastic Modulus (Hot #9)
Non-specified real values are assigned a value of 0.0 by this interface.
If the delta coordinates are not specified, they default to zero. If the To/From fields are not specified, it is considered an
error.
An 18-member array (IEL) contains the pointers to the auxiliary data arrays. The IEL array is dimensioned (N1,18).
NOTE, at this time, only 14 of the members of this array are utilized!
Use FORTRAN format (2X, 6I13) to write the values of the following 14 items on the next three lines of the neutral file.
1 Pointer to Bend Auxiliary field. This indicates where in the bend auxiliary array the bend data for the current element
can be found.
2 Pointer to Rigid Element Auxiliary field.
3 Pointer to Expansion Joint Auxiliary field.
4 Pointer to Restraint Auxiliary field.
5 Pointer to Displacement Auxiliary field.
6 Pointer to Force/Moment Auxiliary field.
7 Pointer to Uniform Load Auxiliary field.
8 Pointer to Wind Load Auxiliary field.
9 Pointer to Element Offset Auxiliary field.
10 Pointer to Allowable Stress Auxiliary field.
11 Pointer to Intersection Auxiliary field.
12 Pointer to Node Name Auxiliary field.
13 Pointer to Reducer Auxiliary field.
14 Pointer to Flange Auxiliary field.
A pointer value of zero should be used where there is no auxiliary data of a particular type associated with the current
element.
Auxiliary Element Data
#$ AUX_DATA. This is the section division header. The #$ and space are required, as well as the word AUX_DATA, all in
capital letters.
This section of the file contains the auxiliary data corresponding to the elements. This data is arranged in the same order as
the IAUXAU array described previously. For example, if IAUXAU(1) contains a 3, then there are 3 bends in the model, and
their data is found next in the neutral file. Also assume that IAUXAU(2) contains a 5, then there are 5 rigid elements in the
model and their data follows the bend data.
Chapter 8 Interfaces 8-61
Each set of auxiliary data is separated by a sub-section header. If a particular value in IAUXAU is zero, then only the
subsection header is written to the neutral file.
The data storage for these arrays is allocated at run time, based on the available free system memory. These arrays are
allocated proportionally, as a percentage of the n-umber of elements allowed. Four proportions are used: 1/2, 1/3, 1/4, and
1/5. These proportions correspond to the variables: N2, N3, N4, and N5. Maintaining these proportions ensures that the
neutral file reader can accept the file.
#$ NODENAME. This is the subsection header that defines the start of Node Name data. (In order to maintain downward
compatibility, this section is optional.) The data for each element set of node names in the input file is listed here.
A two-member array (NAM) defines each set of node names. The NAM array is dimensioned (N6, 2). Use FORTRAN
format (2X, A10, 16X, A10) to read first the character name of the FROM node and then that of the TO node.
#$ BEND. This is the subsection header that defines the start of the bend data. The data for each bend in the input file is
listed here.
An 11-member array (BND) defines each bend. The BND array is dimensioned (N3,11).
Use FORTRAN format (2X, 6G13.6) to write the values of the following 11 items on the next two lines of the neutral file.
1 bend radius
2 type: 1 - single flange 2 - double flange 0 or blank - welded
3 angle to node position #1
4 node number at position #1
5 angle to node position #2
6 node number at position #2
7 angle to node position #3
8 node number at position #3
9 number of miter cuts
10 fitting thickness of bend if different from the pipe
11 Seam Weld (1=Yes, 0=No)
12 Bend flexibility (K) factor
#$ RIGID. This is the subsection header that defines the start of the rigid data. The data for each rigid in the input file is
listed here.
A single-element array (RIG) for each rigid. The RIG array is dimensioned (N3,1). The single element of the array
represents the rigid weight.
Use FORTRAN format (2X, 6G13.6) to write the value.
#$ EXPJT. This is the subsection header that defines the start of the expansion joint data. The data for each expansion joint
in the input file is listed here. The EXP array is dimensioned (N5,5).
Use FORTRAN format (2X, 6G13.6) to write the values of the following five items on the next line of the neutral file.
8-62 Interfaces
1 axial stiffness
2 transverse stiffness
3 bending stiffness
4 torsional stiffness
5 effective inside bellows diameter
#$ RESTRANT. This is the subsection header that defines the start of the restraint data.
The data for each restraint auxiliary data block in the input file is listed here. The RES array is dimensioned (N2,36).
Use FORTRAN format (2X, 6G13.6) to write the values of the following nine items on the next two lines of the neutral file.
These nine items are repeated four times for the four possible restraints defined in the auxiliary data block.
This will require two lines in the neutral file for each restraint specification, which means eight lines total for each restraint
auxiliary.
1 restraint node number
2 restraint type (see additional notes to follow)
3 restraint stiffness
4 restraint gap
5 restraint friction coefficient
6 restraint connecting node
7 X direction cosine
8 Y direction cosine
9 Z direction cosine
Note: Items 3-9 may change based on the value of the restraint type. For more information refer to the help text for more
information.
The restraint type is an integer value whose valid range is from 1 to 62.
The 62 possible restraint types are
#$ DISPLMNT. This is the subsection header that defines the start of the displacement data.
The data for each displacement auxiliary data block in the input file is listed here.
Chapter 8 Interfaces 8-63
Use FORTRAN format (2X, 6G13.6) to write the values of the following 55 items on the next lines of the neutral file. The
DIS array is dimensioned (N3,110).
This will require ten lines in the neutral file for each displacement specification, which means 20 lines total for each
displacement auxiliary.
These 55 items are repeated 2 times for the two possible displacements defined on the auxiliary.
Note: Unspecified displacement values (i.e., free-displacement degrees of freedom) are designated through the use of a
value of 9999.99.
#$ FORCMNT. This is the subsection header that defines the start of the force/moment data. The data for each
force/moment auxiliary data block in the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following 55 items on the next ten lines of the neutral file.
The FOR array is dimensioned (N3,38).
This will require ten lines in the neutral file for each force/moment specification, which means 20 lines total for each
force/moment auxiliary data block.
8-64 Interfaces
#$ UNIFORM. This is the subsection header that defines the start of the uniform load data. The data for each uniform load
in the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following 9 items on the next two lines of the neutral file.
The UNI array is dimensioned (N5,9).
This will require two lines in the neutral file for each uniform load auxiliary data block.
{vector 1 & 2}
UX1 UY1 UZ1 UX2 UY2 UZ2
{vector 3}
UX3 UY3 UZ3
#$ WIND. This is the subsection header that defines the start of the wind/wave data. The data for each wind/wave
specification in the input file is listed here. The WIND array is dimensioned (N5,5).
Use FORTRAN format (2X, 6G13.6) to write the set of values on the next line of the neutral file. This will require a single
line in the neutral file for each wind auxiliary.
The five data items on each line are as follows:
1 entry type (0.0 for Wind, 1.0 for Wave, 2.0 for Off)
2 wind shape factor or wave drag coefficient
3 wave added mass coefficient
4 wave lift coefficient
5 wave marine growth
#$ OFFSETS. This is the subsection header that defines the start of the element offset data. The data for each offset pipe in
the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following six items on the next line of the neutral file. The
OFF array is dimensioned (N5,6).
This will require a single line in the neutral file for each offset auxiliary.
Chapter 8 Interfaces 8-65
1 element FROM node offset in X direction
2 element FROM node offset in Y direction
3 element FROM node offset in Z direction
4 element TO node offset in X direction
5 element TO node offset in Y direction
6 element TO node offset in Z direction
#$ ALLOWBLS. This is the subsection header that defines the start of the allowable stress data. The data for each
allowable spec in the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following 108 items on the next eighteen lines of the neutral
file. The ALL array is dimensioned (N5,108).
This will require eighteen lines in the neutral file for each allowable auxiliary.
1 cold allowable stress
2 hot allowable for thermal case #1
3 hot allowable for thermal case #2
4 hot allowable for thermal case #3
5 code cyclic reduction factor for thermal case #1
6 code cyclic reduction factor for thermal case #2
7 code cyclic reduction factor for thermal case #3
8 Eff.
9 Sy
10 fac
11 Pmax
12 piping code id
13 hot allowable for thermal case #4
14 hot allowable for thermal case #5
15 hot allowable for thermal case #6
16 hot allowable for thermal case #7
17 hot allowable for thermal case #8
18 hot allowable for thermal case #9
19 code cyclic reduction factor for thermal case #4
20 code cyclic reduction factor for thermal case #5
21 code cyclic reduction factor for thermal case #6
22 code cyclic reduction factor for thermal case #7
23 code cyclic reduction factor for thermal case #8
24 code cyclic reduction factor for thermal case #9
25 cycles for BW (butt-weld) fatigue pair #1
26 cycles for BW fatigue pair #2
8-66 Interfaces
27 cycles for BW fatigue pair #3
28 cycles for BW fatigue pair #4
29 cycles for BW fatigue pair #5
30 cycles for BW fatigue pair #6
31 cycles for BW fatigue pair #7
32 cycles for BW fatigue pair #8
33 stress for BW fatigue pair #1
34 stress for BW fatigue pair #2
35 stress for BW fatigue pair #3
36 stress for BW fatigue pair #4
37 stress for BW fatigue pair #5
38 stress for BW fatigue pair #6
39 stress for BW fatigue pair #7
40 stress for BW fatigue pair #8
41 cycles for FW (fillet-weld) fatigue pair #1
42 cycles for FW fatigue pair #2
43 cycles for FW fatigue pair #3
44 cycles for FW fatigue pair #4
45 cycles for FW fatigue pair #5
46 cycles for FW fatigue pair #6
47 cycles for FW fatigue pair #7
48 cycles for FW fatigue pair #8
49 stress for FW fatigue pair #1
50 stress for FW fatigue pair #2
51 stress for FW fatigue pair #3
52 stress for FW fatigue pair #4
53 stress for FW fatigue pair #5
54 stress for FW fatigue pair #6
55 stress for FW fatigue pair #7
56 stress for FW fatigue pair #8
Items 57 through 108 are for the TD/12 piping code.
Some of these items (notably 8-24) may have various meanings based on the active piping code.
#$ SIF&TEES. This is the subsection header that defines the start of the SIF/TEE data. The data for each SIF/TEE spec in
the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following 30 items, for each of the two tees that can be
specified on the dialog. The SIF array is dimensioned (N4,60).
This will require five lines in the neutral file for each SIF/TEE specified, which means ten lines total for each auxiliary.
Chapter 8 Interfaces 8-67
1 intersection node number
2 intersection type code, if not specified this auxiliary is only used to specify SIFs
3 SIF, in plane
4 SIF, out of plane
5 Weld id
6 Fillet
7 Pad thk
8 FTG Ro
9 crotch
10 weld id
11 B1
12 B2
Items 13 - 30 are for the TD/12 piping code.
#$ REDUCERS. This is the subsection header that defines the start of the REDUCER data. The data for each REDUCER
spec in the input file is listed here.
Use FORTRAN format (2X, 6G13.6) to write the values of the following 5 items on the next line of the neutral file. The
RED array is dimensioned (N6,5).
This will require one line in the neutral file for each REDUCER specified.
1 2nd diameter of the reducer
2 2nd thickness of the reducer
3 alpha angle of the reducer
4 R1 value of the reducer for the TD/12 piping code
5 R2 value of the reducer for the TD/12 piping code
These values are repeated for the second intersection specification.
#$ FLANGES. This is the subsection header that defines the start of the FLANGE data. The data for each FLANGE spec in
the input file is listed here. There are 72 data values used to describe a flange, as shown here:
1 FROM/TO (0 = FROM, 1 = TO, 2= BOTH)
2 METHOD (0 = PEQ, 1 = ASME NC)
3 GASKET OR BOLT CIRCLE DIAMETER, DEPENDING ON METHOD
4 BOLT AREA (ASME METHOD ONLY)
5 SYC (ASME METHOD ONLY)
6 SY1 (ASME METHOD ONLY)
8-68 Interfaces
7 SY2 (ASME METHOD ONLY)
8 SY3 (ASME METHOD ONLY)
9 SY4 (ASME METHOD ONLY)
10 SY5 (ASME METHOD ONLY)
11 SY6 (ASME METHOD ONLY)
12 SY7 (ASME METHOD ONLY)
13 SY8 (ASME METHOD ONLY)
14 SY9 (ASME METHOD ONLY)
15-24 CLASS NAME, (40 CHAR MAX)
25-48 24 TEMPERATURES OF THE TEMP/PRESS RATING CURVE (PEQ METHOD ONLY)
49-72 24 PRESSURES OF THE TEMP/PRESS RATING CURVE (PEQ METHOD ONLY)
These values are arranged in the neutral file on 12 lines, as follows, using a format of (2X, 6G13.6) unless otherwise
specified:
Line 1: Flange items 1-5
Line 2: Flange items 6-11
Line 3: Flange items 12-14
Line 4: Class Name, using a format of (2X, A40)
Line 5: Flange items 25-30
Line 6: Flange items 31-36
Line 7: Flange items 37-42
Line 8: Flange items 43-48
Line 9: Flange items 49-54
Line 10: Flange items 55-60
Line 11: Flange items 61-66
Line 12: Flange items 67-72
All 12 lines must be written to the neutral file for each flange. Unused fields/values can be represented by 0.00.
Miscellaneous Data Group #1
#$ MISCEL_1. This is the section division header. The #$ and space are required, as well as the word MISCEL_1, all in
capital letters.
Chapter 8 Interfaces 8-69
The data in this group consists of the material id (RRMAT) for each element in the input file, the nozzle data (VFLEX), the
hanger data, and the execution options.
Material ID. The first array in this section (RRMAT) contains the material id number for each element in the input file. Use
FORTRAN format (2X, 6G13.6).
The RRMAT array is dimensioned (N1). The material ids range from 1 to 699 ( See the Users Guide for details).
The number of lines required to write the RRMAT array in the neutral file is determined by the following FORTRAN
routine:
NLINES = NUMELT / 6
IF(MOD(NUMELT,6).NE.0)THEN
NLINES = NLINES + 1
ENDIF
Nozzles. The next set of data describes the flexible (WRC-297, PD-5500, API 650) nozzles in the input file.
Note: 9999.99 represents infinity.
Use FORTRAN format (2X, 6G13.6). The nozzle (VFLEX) contains 16 values for each nozzle in the input.
This will require four lines in the neutral WRC-297, PD-5500, and/or API 650 spreadsheet. The VFLEX array is
dimensioned (N6, 16).
For WRC-297 nozzles, the 16 items are
1 Nozzle Node Number
2 Vessel Node Number (optional)
3 Nozzle type indicator (-1.0101 = 297, 1.0 = 650)
4 Nozzle Outside Diameter (in.)
5 Nozzle Wall Thickness (in.)
6 Vessel Outside Diameter (in.)
7 Vessel Wall Thickness (in.)
8 Vessel Reinforcing Pad Thickness (in.)
9 Spare (not used)
10 Dist. to stiffeners or head (in.) (9999.99 = )
11 Dist. to opposite side stiffeners or head (in.) (9999.99 = )
12 Vessel centerline direction vector X
13 Vessel centerline direction vector Y
14 Vessel centerline direction vector Z
15 Vessel Temperature (optional) (F)
16 Vessel Material # (optional)(1-17)
8-70 Interfaces
For PD-5500 nozzles, the 16 items are
1 Nozzle Node Number
2 Vessel Node Number (optional)
3 Nozzle type indicator (2.0-5500)
4 Vessel Type (0-Cylinder, 1-Sphere)
5 Nozzle Outside Diameter (in.)
6 Vessel Outside Diameter (in.)
7 Vessel Wall Thickness (in.)
8 Vessel Reinforcing Pad Thickness (in.)
9 Spare (not used)
10 Dist. to stiffeners or head (in.) (9999.99 = )
11 Dist. to opposite side stiffeners or head (in.) (9999.99 = )
12 Vessel centerline direction vector X
13 Vessel centerline direction vector Y
14 Vessel centerline direction vector Z
15 Vessel Temperature (optional) (F)
16 Vessel Material # (optional) (1-17)
For API 650 nozzles, the 16 items are
1 Nozzle Node Number
2 Vessel Node Number (optional)
3 Nozzle type indicator (1.0 = 650)
4 Nozzle Outside Diameter (in.)
5 Nozzle Wall Thickness (in.)
6 Vessel Outside Diameter (in.)
7 Vessel Wall Thickness (in.)
8 Spare (not used)
9 Reinforcing on 1 - shell, or 2 - nozzle
10 Height of nozzle centerline (in.)
11 Height of tank fluid (in.)
12 Not Used
13 Specific gravity of fluid
14 Thermal expansion coefficient (in/in/deg)
15 Delta Temperature (F)
16 Elastic Modulus (psi)
Hangers. The next set of data describes the spring hangers in the input file. Some of the hanger data listed below represents
uninitialized data. In the instances where this uninitialized data represent infinite values (such as maximum travel limit and
available space) it is reported here as 9999.99.
Chapter 8 Interfaces 8-71
The next line contains values for the following parameters in FORTRAN format (2X, I13, 5G13.6):
IDFTABLE is the default hanger table.
DEFVAR is the default for allowed load variation.
DEFRIG is the default for rigid support displacement criteria.
DEFMXTRAVEL is the default for maximum allowed travel.
DEFSHTSPR is the default for allowing short range springs (0=no 1=yes).
DEFMUL is the default multi load case design option.
The next line contains values for the following parameters in FORTRAN format (2X, 5I13):
IDFOPER is the default # of hanger design operating cases (always 1)
IACTCLD is the default cold load calculation switch (0=no, 1=yes).
IHGRLDS is the number of hanger operating loads (0 -3).
IACTUAL is the load case defining actual cold loads.
IMULTIOPTS is the multiple load case design option (1-7).
An array of hanger node numbers (IHGRNODE) is read/written for each hanger in the input file and is dimensioned (N5).
There will be seven lines in the neutral file for this data, if all N5 hangers are specified. Use FORTRAN format (2X, 6I13).
A 10-element array (HGRDAT) is read/written for each hanger in the input file. The HGRDAT array is dimensioned
(10,N5). Each hanger in the model will require two lines in the neutral file. Use FORTRAN format (2X, 6G13.6).
1 hanger stiffness
2 allowable load variation
3 rigid support displacement criteria
4 allowed space for hanger
5 cold load #1 (theoretical)
6 hot load #1 (initialize to 0.0)
7 user defined operating load f/ variable springs (init to 0.0)
8 maximum allowed travel limit
9 multiple load case design option
10 hanger constant effort support load
A four-element array (IHGRFREE) is read/written for each hanger in the input file. The IHGRFREE array is dimensioned (
4,N5). Each hanger in the file will require one line in the neutral file.
Use FORTRAN format (2X, 6I13).
1 anchor node to be freed (#1)
2 anchor node to be freed (#2)
3 d.o.f. type for #1 (1-free Y, 2-free XY, 3-free ZY, 4-free X, Y, Z, 5-free all)
4 d.o.f. type for #2
An array (IHGRNUM) lists the number of hangers at this location, for each hanger in the input file. There will be one entry
here for every hanger in the file. The IHGRNUM array is dimensioned (N5). There will be seven lines in the neutral file for
this data, if all N5 hangers are specified. Use FORTRAN format (2X, 6I13).
8-72 Interfaces
An array (IHGRTABLE) listing the hanger table numbers for each hanger in the input file. There will be one entry here for
every hanger in the file. The IHGRTABLE is dimensioned (N5). There will be seven lines in the neutral file for this data, if
all N5 hangers are specified. Use FORTRAN format (2X, 6I13).
An array of flags (IHGRSHORT) indicates if short range springs can be used at each hanger location. The IHGRSHORT
array is dimensioned (N5). There will be seven lines in the neutral file for this data. Use FORTRAN format (2X, 6I13).
0 = cant use short range springs
1 = can use short range springs
An array of connecting node numbers (IHGRCN) is available for each hanger. The IHGRCN array is dimensioned (N5).
There will be seven lines in the neutral file for this data, if all N5 hangers are specified. Use FORTRAN format (2X, 6I13).
Execution Options. The next section of data defines the execution options used by the program. Use FORTRAN format
(2X, 4I13, G13.6, I13). This will require three lines in the neutral file. These values are
Print forces on rigids and expansion joints 0=no, 1=yes
Print alphas & pipe props. during error checking 0=no, 1=yes
Activate Bourdon Pressure Effects 0, 1, or 2
Activate Branch Error and Coordinate Prompts 0=no, 1=yes
Thermal Bowing Delta Temperature degrees
Use Liberal Stress Allowable 0=no, 1=yes
For the following data, use FORTRAN format: (2X, I13, 2G13.6, 3I13):
Uniform Load Input in gs 0=no, 1=yes
Stress Stiffening due to Pressure 0, 1, 2
Ambient Temperature (If not 70.00 deg F ) degrees
FRP Expansion * 1,000,000 len/len/deg
Optimizer 0-Both, 1-CuthillMcKee, 2-Collins
Next Node Selection 0-Decreasing, 1-Increasing
For the following data, use FORTRAN format (2X, 4I13, G13.6, I13):
Final Ordering 0-Reversed, 1-Not Reversed
Collins Ordering 0-Band, 1-No. of Coefficients
Degree Determination 0-Connections, 1-Band
User Control 0-None, 1-Allow User Re-Looping
FRP Shear ratio
Laminate type
Units Conversion Data
#$ UNITS. This is the section division header. The #$ and space are required, as well as the word UNITS. The data in this
section defines both the conversion constants as well as the conversion labels. The conversion constants are all REAL*4
values in FORTRAN format (2X, 6G13.6). This will require four lines in the neutral file. The following are character
definitions for the labels:
CNVLEN is the length conversion.
CNVFOR is the force conversion.
CNVMAS is the mass conversion.
CNVMIN is the moment (input) conversion.
CNVMOU is the moment (output) conversion.
Chapter 8 Interfaces 8-73
CNVSTR is the stress conversion.
CNVTSC is the temperature conversion.
CNVTOF is the temperature offset.
CNVPRE is the pressure conversion.
CNVYM is Youngs modulus conversion.
CNVPDN is the pipe density conversion.
CNVIDN is the insulation density conversion.
CNVFDN is the fluid density conversion.
CNVTSF is the translational stiffness conversion.
CNVUNI is the uniform load conversion.
CNVWND is the wind load conversion
CNVELE is the elevation conversion
CNVCLN is the compound length conversion
CNVDIA is the diameter conversion
CNVTHK is the wall thickness conversion
Next, enter the following units labels, one per line, in the format given in the label descriptions. This will require 24 lines
in the neutral file.
CCVNAME - name of the units used, i.e. english, si, ..(CHARACTER*15)
CCVNOM - on or off and tells PREPIP whether or not nominal diameters are allowed (CHARACTER* 3).
CCVLEN - length label (CHARACTER* 3)
CCVFOR - force label (CHARACTER* 3)
CCVMAS - mass label (CHARACTER* 3)
CCVMIN - moment (input) label (CHARACTER* 6)
CCVMOU - moment (output) label (CHARACTER* 6)
CCVSTR - stress label (CHARACTER*10)
CCVTSC - temperature label (CHARACTER* 1)
CCVTOF - temperature offset/label (CHARACTER* 1)
CCVPRE - pressure label (CHARACTER*10)
CCVYM - youngs modulus label (CHARACTER*10)
CCVPDN - pipe density label (CHARACTER*10)
CCVIDN - insulation density label (CHARACTER*10)
CCVFDN - fluid density label (CHARACTER*10)
CCVTSF - translational stiffness label (CHARACTER* 7)
8-74 Interfaces
CCVRSF - rotational stiffness label (CHARACTER*10)
CCVUNI - uniform load label (CHARACTER* 7)
CCVGLD - gravitional load label (CHARACTER* 3)
CCVWND - wind load label (CHARACTER*10)
CCVELE - elevation label (CHARACTER* 3)
CCVCLN - compound length label (CHARACTER* 3)
CCVDIA - diameter label (CHARACTER* 3)
CCVTHK - wall thickness label (CHARACTER* 3)
Nodal Coordinate Data
#$ COORDS. This is the section division header. The #$ and space are required, as well as the word COORDS, all in
capital letters. This section only exists in Versions 3.22 and later.
The data in this section of the neutral file is optional; it may not exist. The existence of this data depends on the users
preference and the particular job. This section of the neutral file is used to specify the X, Y, Z global coordinates of the
starting node point of each discontinuous piping segment. This data, if it exists, is defined below.
The NXYZ value defines how many sets of coordinates follow. Use FORTRAN format (2X, I13).
INODE, XCORD, YCORD, ZCORD This line of four values is repeated NXYZ times.
Use FORTRAN format (2X, I13, 3F13.4) to define a node number and its X, Y, Z global coordinates.
Data Matrix Interface
CAESAR II offers an alternative neutral file, the Data Matrix Interface.
The generic CAESAR II data matrix input routine creates a CAESAR II file from a simple neutral file. It expects to read a file
that contains a single line of data for each pipe in the model. Each line of data contains twelve parameters as follows:
ELMT N1 N2 DX DY DZ DIAM THK ANCH BEND BRAD RIGID
Where:
ELMT is the element number, sequential from 1.
N1 is the from node number.
N2 is the to node number.
DX is the delta dimension in the global X direction.
DY is the delta dimension in the global Y direction (the Y axis is vertical in CAESAR II).
DZ is the delta dimension in the global Z direction.
DIAM is the actual pipe diameter.
THK is the actual pipe wall thickness.
ANCH is a restraint flag, 1 if the from node is restrained, 0 otherwise. Currently ignored.
BEND is a bend indicator, 1 if the element has a bend at the to node, 0 otherwise.
BRAD is the bend radius if not a long radius bend.
Chapter 8 Interfaces 8-75
Important: RIGID is a rigid element flag, 1 if the element is rigid, 0 otherwise.
All values in the matrix should be real, floating point numbers. The format for each line of data should be (12E13.6). This
generic interface does prompt for an arbitrary conversion constant for the delta dimensions and the diameter /thickness
values to overcome any differences between the assumed units of the neutral file and the CAESAR II defaults.
Users developing an interface from scratch are urged to use the Complete Neutral File interface discussed in the next
section. The Data Matrix Interface discussed above transfers the piping geometry only, which requires the analyst to input
additional data to complete the stress model.
8-76 Interfaces
Computational Interfaces
LIQT Interface
The CAESAR II / LIQT Transfer program is used to generate CAESAR II dynamic input data files containing response spectra
for input files which contain the dynamic pipe forces. These time history loads are determined by the Stoner Associates, Inc.
(SAI) LIQT package, from pressure transient loading. The CAESAR II / LIQT Transfer program reads the output file generated
by LIQT, extracts the information needed, and generates the response spectra. Then, the generated response spectrum files
can be used for the dynamic analysis in CAESAR II.
How to Use the CAESAR II / LIQT Interface
When the user reaches the LIQT Transfer module, the following input is required from the user in order to process the
LIQT data:
LIQT output file name. (This file is generated by SAIs LIQT package with extension .FRC)
Names of LIQT nodes which identify the pipes that response spectra are to be generated for.
Corresponding CAESAR II node numbers for the LIQT pipes.
Maximum number of points on each generated response spectrum curve.
Frequency cut off value.
After the proper user input data is acquired, the LIQT interface module starts the data transfer. During the computation, the
user will be apprised of the process status. The user can click the Cancel button at any time to abort the computation.
The resulting force spectrum files (DLF curves) are written to the CAESAR II data directory during the computation phase of
the program. The names of generated force spectrum files have the following format:
L*.DLF where "*" is the user CAESAR II node number in the piping model which corresponds to the equivalent LIQT pipe
name.
When all computations have completed, the user will be returned to the CAESAR II Main Menu.
Technical Discussion of LIQT Interface
Normal piping system operating procedures such as pump start-up and shutdown, valve closure, and unexpected events such
as power failure, may produce unsteady pressure-flow conditions. A piping system with rapid pressure-flow variations must
be carefully designed to prevent devastating results.
SAIs LIQT package performs the analysis and simulation of the unsteady flow situations for a particular liquid piping
system, and generates the piping load time histories for the pressure transient of this particular liquid piping system.
In the dynamic analysis module of CAESAR II, a response spectrum can be generated from the user input of time history
pulse. However, there are typically too many data points from a time history analysis for a user to manually input the data
into CAESAR II. The CAESAR II LIQT Transfer is used to bridge the gap between SAIs LIQT package and the CAESAR II
dynamic analysis module.
After the time history loads have been generated by SAIs LIQT package, the CAESAR II LIQT Interface extracts the dynamic
pipe forces from the LIQT generated file, and computes the response spectrum. Afterward, the response spectrum can be
used as the DLF curve for the dynamic analysis in CAESAR II.
The response spectrum is a plot giving the maximum response of all possible linear one degree of freedom systems due to a
given input, which in the present case is a force. The abscissa of the spectrum is the frequency axis, and the ordinate is the
maximum response, i.e. the dynamic load factor (DLF). The DLF is the ratio of the dynamic deflection at any time to the
deflection which would have resulted from the static application of the load. In cases where the applied load is not constant,
the maximum load which occurs at any time during the period of interest is taken.
Chapter 8 Interfaces 8-77
The dynamic load factor is non dimensional and independent of the magnitude of load. The following examples illustrate
the characteristics of the DLF curve in terms of the magnitude and the duration of the load.
Example 1
Find the DLF response spectrum of the trapezoidal pulse loads shown in the following figure.
Force vs. Time
Solution: The response spectra generated from all four pulse loads are identical, as shown in the following figure.
DLF vs. Frequency
The result shows that the DLF curve is independent of the magnitude of the pulse load.
8-78 Interfaces
Example 2
Find the response spectrum of the following trapezoidal pulse loads.
Force vs. Time
Force vs. Time
Chapter 8 Interfaces 8-79
Force vs. Time
Solution: The plotted results displayed in Figure 13.11 show that the longer the duration of the force the higher the DLF.
The triangular pulse, which has a duration of zero, generates the lowest DLF curve.
DLF vs. Frequency
PIPENET Interface
The CAESAR II / PIPENET Transfer program is used to generate CAESAR II dynamic input data files containing response
spectra for input files which contain the dynamic pipe forces. These time history loads are determined by the Sunrise
System's Pipenet package, from pressure transient loading. The CAESAR II / PIPENET Transfer program reads the output file
generated by PIPENET, extracts the information needed, and generates the response spectra. Then, the generated response
spectrum files can be used for the dynamic analysis in CAESAR II.
8-80 Interfaces
How to Use the CAESAR II / PIPENET Interface
When users reach the PIPENET Transfer module, the following inputs are required to process the PIPENET data:
PIPENET output file name. (This file is generated by Sunrise System's PIPENET package with extension .FRC)
Names of PIPENET pipes whose response spectra are to be generated for.
Corresponding CAESAR II node numbers for the PIPENET pipes.
Maximum number of points on each generated response spectrum curve.
Frequency cut off value.
After the proper user input data is acquired, the PIPENET interface module starts the data transfer. During the computation,
the user will be apprised of the process status. Users can click Cancel at any time to abort the computation.
The resulting force spectrum files (DLF curves) are written to the CAESAR II data directory during the computation phase of
the program. The names of generated force spectrum files have the following format:
P*.DLF where "*" is the user's CAESAR II node number in the piping model which corresponds to the equivalent PIPENET
pipe name.
Further, the PIPENET Interface creates a complete CAESAR II Dynamic Input file including spectrum definition, force sets,
load cases, and combination load cases. The resulting input file is ready to be run "as is" or can be further modified by the
user.
When all computations have completed, users are returned to the CAESAR II Main Menu.
Technical Discussion of the PIPENET Interface
Normal piping system operating procedures such as pump start-up and shutdown, valve closure, and unexpected events such
as power failure, may produce unsteady pressure-flow conditions. A piping system with rapid pressure-flow variations must
be carefully designed to prevent devastating results.
PIPENET performs the analysis and simulation of the unsteady flow situations for a particular liquid piping system, and
generates the piping load time histories for the pressure transient of this particular liquid piping system.
In the dynamic analysis module of CAESAR II, a response spectrum can be generated from the user input of time history
pulse. However, there are typically too many data points from a time history analysis for a user to manually input the data
into CAESAR II. The CAESAR II PIPENET Transfer is used to bridge the gap between PIPENET and the CAESAR II dynamic
analysis module.
After the time history loads have been generated by PIPENET, the CAESAR II PIPENET Interface extracts the dynamic pipe
forces from the PIPENET generated file, and computes the response spectrum. Afterward, the response spectrum can be
used as the DLF curve for the dynamic analysis in CAESAR II.
The response spectrum is a plot giving the maximum response of all possible linear one degree of freedom systems due to a
given input, which in the present case is a force. The abscissa of the spectrum is the frequency axis, and the ordinate is the
maximum response, i.e. the dynamic load factor (DLF). The DLF is the ratio of the dynamic deflection at any time to the
deflection which would have resulted from the static application of the load. In cases where the applied load is not constant,
the maximum load which occurs at any time during the period of interest is taken.
The dynamic load factor is non dimensional and independent of the magnitude of load.
Chapter 8 Interfaces 8-81
Data Export to ODBC Compliant Databases
CAESAR II permits the export of the analysis results to ODBC compliant databases. ODBC is a programming interface that
enables applications to access data in database management systems that use Structured Query Language (SQL) as a data
access standard. CAESAR II uses two drivers supplied by Microsoft Corporation to communicate with the Access database or
Excel spreadsheet. These drivers are installed by default when either of the two products is set up on a system.
DSN Setup
In order to use the CAESAR II data export facility, you need to set up two Data Source Names (DSNs) on the system. DSNs
contain information regarding where the database resides on the computer and how to communicate with it, i.e. what driver
to use. CAESAR II has capabilities to export data to either an Access database or an Excel spreadsheet. Therefore, you will
need two DSNs set up to allow use of this feature. The names of these two DSNs are FIXED by COADE Inc.
The CAESAR II installation program is designed to set up these DSNs automatically. However, in the event that the DSNs
are not set up, use the procedure listed below.
Setting Up the Data Source Name:
1 Click the Start button and select Settings and then Control Panel.
2 Double-click on ODBC Data Sources icon and select the User DSN tab.
3 Click the Add button. A window similar to the following will display.
Create New Data Source
8-82 Interfaces
Important: Follow steps 4 through 8 for Microsoft Access DSN Setup ONLY! Skip to step 9 for Microsoft Excel
DSN Setup.
4 Select the Microsoft Access Driver (*.mdb) and click the Finish button. A window similar to the one below will
display and you will be prompted to select your database.
Access DSN Setup
The data source name MUST be the C2_OUT_ACCESS. The description is an optional field and can hold any description
information.
5 Enter the Data Source Name and the Description, and click the Select button to select the CAESAR II template database.
CAESAR II is supplied with a template database that contains the structure to hold data exported from the program. For
Access: this file is named caesarII.mdb and will be present in the system directory of your CAESAR II installation
directory.
6 Select the file and click the OK button as shown in the following figure.
Select Database Window
Chapter 8 Interfaces 8-83
After completing the previous step, you will be returned to the ODBC Microsoft Access Setup window similar to the
following figure.
Access Setup Screen After Database Selection
7 Click the OK button and a window similar to the one below will be displayed. Note that C2_OUT_ACCESS has been
added to list of available user DSNs.
User DSN Tab After Adding Access DSN
8-84 Interfaces
You have now successfully completed the Access DSN setup.
Note: This above process needs to be performed only once per machine.
Controlling the Data Export
The CAESAR II data export is controlled using the Setup/Configuration module. By default, data export is disabled. You
must run Configure/Setup to enable ODBC data export. To set up the ODBC data export in CAESAR II, follow the steps
below.
Setting Up the ODBC Data Export
1 Select CONFIGURE/SETUP on the Tools pull-down menu from the CAESAR II Main Menu.
2 Select the Database Definitions tab.
3 Check the Enable Data Export to ODBC Compliant Databases check box, which will enable the Browse button.
4 Click the Browse button, type the name of your database and save it in a directory of your choice.
Note: CAESAR II will copy the template database to the directory specified and name the database as specified.
The Append re-runs to existing data check box is optional. If left unchecked, re-runs of the same job will overwrite any
existing data for the same job in the database/spreadsheet. If checked, re-runs will add or append data from the new runs to
the database/spreadsheet.
5 Click Exit w/ Save to save changes to the configuration.
Note: As in previous versions of CAESAR II, the configuration file applies to all CAESAR II jobs present in that directory.
Similarly, the external database/spreadsheet specified in one configuration file applies to all jobs present in that directory.
Data Export Wizard
CAESAR II offers an ODBC Wizard for immediate interfacing (in addition to the in-line interfacing offered previously) of
both input and output piping model data. (Note that the input data may only be accessed through the Wizard; while the in-
line interface still transfers only the output data.)
This wizard, besides being compatible with ODBC (Microsoft Access and Excel) can also export data in XML format.
(Note that the Excel interface produces a semicolon delimited text file, which can be imported into Excel very quickly.)
The interface is accessed via the Tools/Eternal Interfaces/Data Export Wizard menu command from the CAESAR II Main
Menu. The Data Export Wizard dialog displays; the exported data set can be developed by responding to the questions
and clicking the Next button.
Chapter 8 Interfaces 8-85
The Input and Output Files dialog requests the name of the CAESAR II piping file (the._A file) for which the data is to be
exported: the user must browse for it.
Activating the Export Output Data Also check box provides the ability to include any output results (if available) to the
exported data set as well. Activating the Use System Units check box converts the data to the set of units currently selected
in the CAESAR II Configure /Setup. Selection of the Data Export Output file designates where the data will go, as well as in
what form the data will be: selection of files with extensions of .MDB, .TXT, or .XML produce data in the form of
Microsoft Access, Microsoft Excel semi-colon delimited text, or XML, respectively.) Note, a great deal of on-line help
is provided for this wizard, accessible via the Help button.
The CAESAR II Input Export Options dialog allows the user to select the input data items that are to be exported.
8-86 Interfaces
If the user has clicked the Export Output Data check box, the CAESAR II Output Export Options dialog allows the user
to select the type of results to be exported, and the load cases for which these results are to be exported.
Clicking finish completes the operation. The resultant data file may now be queried or otherwise manipulated through the
use of Microsoft Access, Microsoft Excel, or XML parsing software. Note that a number of built in reports, queries, and
other helpful items (see the figure above) have been provided in the default Access file format, or the user can develop
custom reports and queries.
Chapter 9 File Sets
This chapter lists the files loaded on your computer when you install CAESAR II and the files that CAESAR II creates for a
particular job.
In This Chapter
CAESAR II File Guide............................................................................ 9-2
Required for Execution............................................................................ 9-3
Required Error Data................................................................................. 9-5
Required Data Set .................................................................................... 9-6
Required Printer/ Listing ......................................................................... 9-9
Dynamics ................................................................................................. 9-11
Auxiliary.................................................................................................. 9-12
Structural Data......................................................................................... 9-13
External Interfaces ................................................................................... 9-14
Examples ................................................................................................. 9-15
CAESAR II Operational (Job) Data Files................................................ 9-16
C H A P T E R 9
9-2 File Sets
CAESAR II File Guide
CAESAR II is composed of a number of files which are loaded onto the hard drive. At the current time, approximately 60
megabytes are required for a complete software installation. If your disk is cramped for space, you may have to manually
delete files from your hard disk before installing a new version of CAESAR II. If you are storing data files in your CAESAR II
installation directory, archive them first before you begin the file deletion process. If you are performing a partial
installation, be sure the directory is clean before you start; otherwise you will have a mixed version and it will not perform
as expected, and CRC errors may be generated during the installation.
If you have adequate space on your hard drive, the new program data files will overwrite the existing data files from the
previous version. Some exceptions, such as the material database file, change from year to year, and may have to be deleted
manually to maximize disk space.
After a successful installation, the following directory structure will exist on the hard disk, assuming the installation
directory was named "caesar."
\caesar contains main program files
\caesar\acrobat contains the Adobe Acrobat Reader installation file
\caesar\assidrv contains HASP device drivers and instructions
\caesar\c2_docu contains the CAESAR II on-line documentation
\caesar\examples contains example jobs
\caesar\lib_i contains CADWorx library file in Imperial units
\caesar\lib_m contains CADWorx library file in Metric units
\caesar\setupesl contains ESL device driver installation routine
\caesar\Spec contains CADWorx specification files
\caesar\ssidrv contains SSI device drivers and instructions
\caesar\system contains program data file templates and libraries
It should be noted that as a disk reaches its capacity, disk access can be slowed considerably. For this reason it is a good
idea to perform some periodic house cleaning on the directory(s) where CAESAR II files are stored. This would involve
deleting scratch files and old job files. The CAESAR II File-Clean Up Files command option can help in this process.
Chapter 9 File Sets 9-3
Required for Execution
Required for Execution Description
ANAHLP01.EXE Help file for dynamic input and load case editor
ANAHLP02.EXE Help file for dynamic input and load case editor
ANAL1.EXE Static load cases/Dynamic input program
ANNOUNCE.EXE Build changes announcement program
C2.EXE Main Menu program
C2DATA.EXE Input conversion to new units program
C2HELP01.EXE Help file
C2HELP02.EXE Help index
C2SET01.EXE Help file
C2SET02.EXE Help index
C2SETUP.EXE Configuration program
C2U.EXE Buried pipe modeler
CRCCHK.EXE CRC check program
ELEM.EXE Element generator
ENGLISH.FIL English units file
EXPJT.HED Generic expansion joint header file
FRP.HED Generic FRP header file
IECHO.EXE Input echo setup/Neutral file program
INCORE.EXE In-core solution module program
M1HELP01.EXE Miscellaneous help file
M1HELP02.EXE Miscellaneous help file
OP2HLP01.EXE Output processor help file
OP2HLP02.EXE Output processor help file
MM.FIL Millimeter units file
OUTCORE.EXE Out-of-core solution module program
OUTP01.EXE Static force/stress computation program
OUTP02.EXE Static output processor
PIERCK.EXE Piping error checker
PREPIP.EXE Piping input module
REPORT.EXE Input list/echo generation program
SI.FIL SI units file
9-4 File Sets
Required for Execution Description
STREAM.EXE Batch stream processor program
TIPS.TXT Start-up Tip-of-the-Day program
TYPE.BIN Parameter definition file TUV.fil
VALVE.HED Generic valve/flange header file
XX.CRC CRC check data file
Chapter 9 File Sets 9-5
Required Error Data
Required Error Data Files Description
C2ER01A.EXE Error explanation text
C2ER01B.EXE Error index file
C2ER01C.EXE Error explanation text
C2ER01D.EXE Error index file
C2ER01E.EXE Error explanation text
C2ER01F.EXE Error index file
C2ER01Z.EXE Error explanation text
C2ER02A.EXE Error index file
C2ER02B.EXE Error explanation text
C2ER02C.EXE Error index file
C2ER02D.EXE Error explanation text
C2ER02E.EXE Error index file
C2ER02F.EXE Error explanation text
C2ER02Z.EXE Error index file
C2ERROR.EXE Error reporting program
9-6 File Sets
Required Data Set
Required Data Set Description
5-110-1A.FAT Material fatigue curve
5-110-1B.FAT Material fatigue curve
5-110-2A.FAT Material fatigue curve
5-110-2B.FAT Material fatigue curve
5-110-2C.FAT Material fatigue curve
ACCESS2K.BAT Batch file to switch to Access 2000
ACCESS97.BAT Batch file to switch to Access 97
AMRN2020.FRP FRP data
AP.BIN ANSI pipe sizes
API650.DIG API650 chart data
APPRVD.BIN Stoomwezen approval certificate
BE.HGR Basic engineering hanger data
BERGEN.HGR Bergen Power hanger data
BHEL.HGR BHEL hanger data
C2MAT.EXE Material database editor
CAESAR.FRP FRP data
CAESARII.MDB Access template file
CAESARI1997I.MDB Access 97 database template
CAESARII2000.MDB Access 2000 database template
CAESARII.XLS Excel template file
CAPITOL.HGR Capitol hanger data
CARPAT.HGR Carpenter & Paterson hanger data
CHINAPWR.HGR China Power hanger data
CMAT.BIN Supplied Material database
CMP_INP.BAT Batch file for compressed input listing
COL_INP.BAT Batch file for column oriented input listings
COMET.HGR Comet Hanger data
CRANE.DAT Crane valve/flange database
CRANE.VHD Crane valve/flange header file
Chapter 9 File Sets 9-7
Required Data Set Description
DP.BIN DIN pipe sizes
ENGLISH.FIL
FLEXIDIR.HGR Flexidir hanger data
FLEXPATH.DAT Flexonics/Pathway Bellows expansion joint database
FLEXPATH.JHD Flexonics/Pathway Bellows header file
FRONEK.HGR Fronek hanger data
GENERIC.DAT Generic valve/flange database
GENERIC.VHD Generic valve/flange header file
ANVIL.HGR Grinnell hanger data
HYDRA.HGR Witzenmann hanger data
HYDRAANG.DAT Witzenmann angular expansion joint database
HYDRAANG.JHD Witzenmann angular expansion joint header file
HYDRAAXI.DAT Witzenmann axial expansion joint database
HYDRAAXI.JHD Witzenmann axial expansion joint header file
HYDRALAT.DAT Witzenmann lateral expansion joint database
HYDRALAT.JHD Witzenmann lateral expansion joint header file
INOFLEX.HGR
IWK_ANG.DAT IWK angular expansion joint database
IWK_ANG.JHD IWK angular expansion joint header file
IWK_AXI.DAT IWK axial expansion joint database
IWK_AXI.JHD IWK axial expansion joint header file
IWK_LAT.DAT IWK lateral expansion joint database
IWK_LAT.JHD IWK lateral expansion joint header file
JP.BIN JIS pipe sizes
LISEGA.HGR Lisega Hanger data
MATFIL1.BIN ASME Sect VIII material database
MM.FIL
MYATT.HGR Myatt Hanger data
MYRICKS.HGR Myricks Hanger data
NHK.hgr NHK Hanger data
9-8 File Sets
Required Data Set Description
NOFLANGE.DAT Valve/flange database (no flanges)
NOFLANGE.VHD Valve/flange header file (no flanges)
NPS.HGR NPS Hanger data
OUTPUT.HED
PDS_MAT.MAP Intergraph PDS material mapping file
PDS_PIPES_CSV Intergraph PDS pipe sizes
POWER.HGR Power Piping Hanger data
PRINTER.FMT Printer Formatting string file
PSC.HGR PSC Hanger data
PSU.HGR Pipe Supports USA data
PTP.HGR PTP Hanger data
PTP-LRG.DAT
PTP-LRG.JHD
PTP-SML.DAT
PTP-SML.JHD
QUALITY. HGR Quality Pipe Supports data
REGISTERPIPE.BAT Batch file to register PIPEDLL.DLL
SARATHI.HGR Sarathi database
SFI-MID.JHD Senior Flexonics expansion joint database header file
SFI-MID.DAT Senior Flexonics expansion joint database
SI.FIL
SINOPEC.HGR Sinopec Hanger data
TD12AL.FAT Material fatigue curve
TD12ST.FAT Material fatigue curve
TITLE.HED
WAVIN55.FRP Fiberglass material data file
WAVIN63.FRP Fiberglass material data file
WAVIN73.FRP Fiberglass material data file
New FRP Files
New HGR Files
New Pipe Size Files
Chapter 9 File Sets 9-9
Required Printer/ Listing Files
Required Printer/ Listing Files Description
LIST.CRC CRC check data file
OUTPUT.HED Dynamic output report headers
TITLE.HED Piping input title page template
SCREEN.TXT Piping input resource file
ALLOW.INP Compressed formatting for allowable stresses
ALLWTD.INP Formatting for TD/12 allowables
API650.INP Formatting for API 650
API6502.INP Alternate formatting for API 650 nozzles
BENDS.INP Compressed formatting for bends
PD5500.INP Formatting for PD5500 nozzles
PD55002.INP Alternate formatting for PD5500 nozzles
CONPARM.INP Compressed formatting for control parameters
COORDS.INP Compressed formatting for coordinates
DISPLACE.INP Compressed formatting for displacements
ELEMENT.INP Compressed formatting for elements, layout 1
ELEMENT0.INP Compressed formatting for elements, layout 2
ELEMENT1.INP Compressed formatting for elements, layout 3
ELEMENT2.INP Compressed formatting for elements, layout 4
ELEMENT3.INP Compressed formatting for elements, layout 5
ELEMTD12.INP Element formatting for TD/12
EXPJTS.INP Compressed formatting for expansion joints
FORCES.INP Compressed formatting for forces
Required Printer/Listing Files Description (continued)
HANGERS.INP Compressed formatting for spring hangers
INITIAL.INP Listing setup
MATERIAL.INP Compressed formatting for materials
MAT_FRP.INP
NOZZLES.INP Compressed formatting for nozzles
9-10 File Sets
Required Printer/ Listing Files Description
OFFSETS.INP Compressed formatting for offsets
RIGIDS.INP Compressed formatting for rigid elements
RIGIDS2.INP Alternate formatting for rigids
SETUP.INP Compressed formatting for setup parameters
SIF&TEE.INP Compressed formatting for SIFs & tees
SIF&TD12.INP
SUPPORTS.INP Compressed formatting for restraints
TITLE.INP Compressed formatting for title page
UNIFORM.INP Compressed formatting for uniform loads
UNITS.INP Compressed formatting for units
WIND.INP Compressed formatting for wind shape factors
ALLOW2.INP Column oriented formatting for allowable stresses
BENDS2.INP Column oriented formatting for bends
DISPLAC2.INP Column oriented formatting for displacements
ELEMENT4.INP Column oriented formatting for elements
EXPJTS2.INP Column oriented formatting for expansion joints
FORCES2.INP Column oriented formatting for forces
HANGERS2.INP Column oriented formatting for spring hangers
MATRIAL2.INP Column oriented formatting for materials
NOZZLES2.INP Column oriented formatting for nozzles
OFFSETS2.INP Column oriented formatting for offsets
RIGIDS2.INP Column oriented formatting for rigid elements
SIF&TEE2.INP Column oriented formatting for SIFs & tees
SUPPORT2.INP Column oriented formatting for restraints
UNIFORM2.INP Column oriented formatting for uniform loads
WIND2.INP Column oriented formatting for wind shape factors
Chapter 9 File Sets 9-11
Dynamics
Dynamics Description
DYN.EXE Dynamic setup/Harmonic Solution
DYNHEAD.BIN Dynamic input screen data
DYNOUT1.EXE Dynamic force/stress computation program
DYNOUT2.EXE Dynamic output reporting program
DYNPLOT.EXE Graphics animation program
DYNSTART.BIN Dynamic input example data
EIGEN.EXE Eigen solution program
9-12 File Sets
Auxiliary
Auxiliary Set Description
ACCTNG.EXE Accounting report generator
BIGPRT.EXE Large print program
C2_MAT.EXE Material database editor
COADEXE.EXE EXE file scanner
DLLVBASE.TXT DLL baseline information
DLLVERSN.EXE DLL version scanner
DLLVERSN.LST DLL data list
HLPROT1.EXE Help file
HLPROT2.EXE Help file index
MAKEUNIT.EXE Units generation program
MATDAT.92 ASME material database
MISC.EXE SIF, WRC297, B31G, Flange program
MISC01.EXE Help file
MISC02.EXE Help file index
NETUSER.BAT
ROT.EXE Equipment analysis program
RUN107.EXE WRC107 program
UCS66.BIN ASME UCS-66 chart data
WRC-2.DIG WRC107 chart data
Chapter 9 File Sets 9-13
Structural Data
Structural Data Description
AISC.EXE AISC unit check program
AISC77.BIN 1977 AISC steel database
AISC89.BIN 1989 AISC steel database
AISCHLP.HLP AISC program help file
AISCHLP.PTR Help index file
AUST90.BIN 1990 Australian steel database
C2S.EXE Structural input program
C2SHL01.EXE Help file for structural input
C2SHL02P.EXE Help file for structural input
GERM91.BIN 1991 German steel database
HELPSTR.HLP Help file for structural input
KOREAN.BIN 1990 Korean structural database
SAFRICA.BIN 1990 South African structural database
UK.BIN United Kingdom structural database
9-14 File Sets
External Interfaces
External Interfaces Description
ACADX.EXE AutoCad DXF generator
ADEV.EXE PRO-ISO interface
APLANT.EXE Autoplant interface
C2CATIA.EXE CCPLANT/CATIA interface
C2DATIN.EXE Generic neutral file interface
C2DXF.DAT AutoCad DXF template file
C2LIQT.EXE LIQT interface
C2PIPNET.EXE PIPENET interface
C2PIP.EXE PipePlus interface
CADPIP.EXE CADPIPE interface
CVISON.EXE ComputerVision interface
DATAEXP.CHM Data export wizard help file
DATAEXP.EXE Data export wizard
INTGRPH.EXE Intergraph interface
ISOMET.EXE Isomet interface
NODSIZ.LSP Autocad node display routine
PCF.EXE PCF interface
PCFDLL.DLL Supporting DLL for PCF interface
PIPEDLL.DLL Supporting DLL for PCF interface
Chapter 9 File Sets 9-15
Examples
Examples Description
45-75 DLF file for HAMMER job
90-110 DLF file for HAMMER job
CRYISM._7.C2 Dynamic input example
CRYISM._A.C2 Dynamic input example
CRYISM._J.C2 static load case data
CRYNOS._7.C2 Dynamic input example
CRYNOS._A.C2 Dynamic input example
CRYNOS._J.C2 static load case data
CRYSTR.STR.C2 Structural input for CRYISM job
FRAME.J.C2 static load case data
FRAME.STR.C2 Structural input example
HAMMER._7.C2 Dynamic input example
HAMMER._A.C2 Dynamic input example
HAMMER._J.C2 static load case data
JACKET._A.C2 Jacketed pipe example input
JACKET._J.C2 static load case data
NUREG9._7.C2 Dynamic input example, NRC benchmark
NUREG9._A.C2 Dynamic input example, NRC benchmark
NUREG9._J.C2 static load case data
OMEGA._A.C2 Omega loop example input
OMEGA._J.C2 static load case data
RELIEF.C2 DLF file for RELIEF job
RELIEF._7.C2 Dynamic input example,
RELIEF._A.C2 Relief Valve example input
RELIEF._J.C2 static load case data
TABLE._7.C2 Dynamic input example, harmonic
TABLE._A.C2 Dynamic input example, harmonic
TABLE._J.C2 Dynamic input example, harmonic
9-16 File Sets
CAESAR II Operational (Job) Data Files
During the input / analysis/ output phases of operation, CAESAR II creates a number of job specific data files. Some of these
data files are used solely by CAESAR II, while others contain either input or output data. This section defines the commonly
encountered files, their purpose, and whether or not they are important for archiving purposes. In most cases, the job files
listed below are not exposed (visible) on the machine. Only when a job is actively being manipulated are these files
exposed. When a job is not active, all of its files are compressed into either a "C2" archive (for piping) or a "C2S" archive
(for structural).
In the list below, an asterisk (*) by the file name indicates it should be saved in order to archive the input data. A double
asterisk (**) indicates the file should be saved to archive output data.
INPUT, Static
._A * Contains the Users spreadsheet input data.
._J * Contains the load case data.
INPUT, Dynamic
._7 * Contains the Users dynamic input data.
INPUT, Structural
.STR * Contains the Users structural input data.
INPUT, Soil
.SOI * Contains the Users soil property data.
Scratch
._B Nodal boundary condition file, created by the piping error checker and used by the analysis modules.
._C Element properties file, created by the piping error checker and used by the analysis modules.
._N Nodal coordinate file, created by the piping error checker and used by the analysis modules.
._R Job control information, created by the piping error checker and used by the analysis modules.
._E Element connectivity file, created by the piping error checker and used by the analysis modules.
._X Structural geometry file for use with piping preprocessor.
._1 Scratch file
._2 Scratch file
._5 Scratch file with intermediate hanger data
._6 Scratch file
.DXF Geometric data file created for input into AUTOCAD
.HAR Harmonic components for animation
.FRQ Harmonic solution frequency & phase data
._L Intermediate harmonic data file
.XYT Animation output data file from time history analysis
Chapter 9 File Sets 9-17
Listing
.MSG Secondary output file with intermediate computation data
.LST Data listing file
.LIS Data listing file
.C2U Buried modeler error check file
Output
._M ** Intermediate output file, contains data generated by the piping error checker and load case setup modules
._P ** Static output data file
._Q ** Actual harmonic displacement data
._S ** Dynamic output data file
._T ** Time history output data file
.OUT User generated output (text) data file
.VAL Intermediate eigenvalue output file
.VEC Intermediate eigenvector output file
.OTL ** Input/Output QA sequencing data file
.WRN Model warning messages from Error Checker
Note: All of these files may not be present for a given job. The presence of a file is dependent on what analysis has been
run.
Chapter 10 Update History
This chapter provides a history of CAESAR II development.
In This Chapter
CAESAR II Initial Capabilities (12/84)................................................... 10-2
CAESAR II Version 1.1S Features (2/86) ............................................... 10-3
CAESAR II Version 2.0A Features (10/86) ............................................ 10-4
CAESAR II Version 2.1C Features (6/87) .............................................. 10-5
CAESAR II Version 2.2B Features (9/88) .............................................. 10-6
CAESAR II Version 3.0 Features (4/90) ................................................. 10-7
CAESAR II Version 3.1 Features (11/90) ............................................... 10-8
CAESAR II Version 3.15 Features (9/91) ............................................... 10-9
CAESAR II Version 3.16 Features (12/91) ............................................. 10-10
CAESAR II Version 3.17 Features (3/92) ............................................... 10-11
CAESAR II Version 3.18 Features (9/92) ............................................... 10-12
CAESAR II Version 3.19 Features (3/93) ............................................... 10-13
CAESAR II Version 3.20 Features (10/93) ............................................. 10-14
CAESAR II Version 3.21 Changes and Enhancements (7/94) ................ 10-15
CAESAR II Version 3.22 Changes & Enhancements (4/95)................... 10-17
CAESAR II Version 3.23 Changes (3/96)............................................... 10-18
CAESAR II Version 3.24 Changes & Enhancements (3/97)................... 10-19
CAESAR II Version 4.00 Changes and Enhancements (1/98) ................ 10-21
CAESAR II Version 4.10 Changes and Enhancements (1/99) ................ 10-22
CAESAR II Version 4.20 Changes and Enhancements (2/00) ................ 10-23
CAESAR II Version 4.30 Changes and Enhancements (3/01) ................ 10-24
CAESAR II Version 4.40 Changes and Enhancements (5/02) ................ 10-25
CAESAR II Version 4.50 Changes and Enhancements (11/03) .............. 10-26
CAESAR II Version 5.00 Changes and Enhancements (11/05) .............. 10-27
CAESAR II Version 5.10 Changes and Enhancements ( 9/07) ............... 10-28
C H A P T E R 1 0
10-2 Update History
CAESAR II Initial Capabilities (12/84)
The following lists detail the addition and modifications made to CAESAR II by version number. These lists correspond to
the major releases of the software and do not reflect items such as: minor releases (1.0P, 2.1D); re-publication of the User
Guide: or additional new modules released to aid users between updates.
Input data spreadsheets featuring data duplication to the next pipe element
Vessel local Flexibility Calculations
Multiple load case spring hanger design
Algebraic load case combinations
Nonlinear restraints with gaps, friction, 2-node, and skewed options
Zero or finite length expansion joints with Tension Only tie-bars
Built in database of pipe materials and properties
B31 code compliance reports
Static and dynamic capabilities, including animated mode shape plots
Extensive input/output graphics
Pressure effects on bends, including consideration of circular or slightly oval cross-sections
Chapter 10 Update History 10-3
CAESAR II Version 1.1S Features (2/86)
Help Windows
AutoCAD Interface
HP Plotter Interface
Batch Execution Opinion
Accounting System
File Handler
Spooled Input Listings
Uniform Load in Gs
Liberal Code Stress Allowable
Cursor Pad and Function Key Implementation in Input Spreadsheets
Plot Menu Single Keystroke Access
Stainless Steel Pipe Schedules
Direct Input of Specific Gravity
Bourdon Pressure Options
Hanger Control Spreadsheet Updates
10-4 Update History
CAESAR II Version 2.0A Features (10/86)
AISC Structural Steel Database with over 800 different structural steel cross-sections.
Keyword/Batch Structural Steel Preprocessor: Same quality CAESAR II graphics with structural steel volume plots,
interactive error checking, extensive interactive help, and fully compatible with CAESAR II piping models.
High Resolution Graphics: EGA support for monochrome and 640x350, 16 color more. Tecmar Graphics Master
support for monochrome and 640x200, 16 color mode. Hercules support for monochrome 720x348 mode.
Graphics: Addition of PAN and RANGE options, improved Zooming, stresses and displaced shapes in color,
hidden lines removed from volume plots, and pipe and structure plotted together.
3D-Graph: Option to plot stresses for all nodes for all load cases on the same plot.
Simultaneous Use Of Two Screens: One monochrome and the other graphics.
WRC 107 Stress Calculations
Units: English and SI standard options, or user may define his own set of unit constants and labels. Output may be
generated in multiple unit sets, and input files may be converted from one unit set to another.
Wind Load Calculations: According to ANSI A58.1-1982, or user may input his own velocity or pressure versus
elevation tables.
Pipe/structure include Option: Piping input from one file may be included in another with a given node and rotational
offset.
Quick Natural Frequency Range Calculations: Computes the number of natural frequencies in any user given range in
the amount of time needed to do a single static solution.
High Resolution Hardcopy Printer Plots
SETUP FILE DIRECTIVES: Users may set the following CAESAR II execution parameters:
- Graphics hardware configurations
- Colors for over 27 different plotted items
- B3.1 reduced intersection options
- Plot/Geometry connection through CNodes options
- Corroded cross section stress calculation options
- Minimum and Maximum allowed bend angle options
- Occasional load factors
- Loop closure tolerance
Chapter 10 Update History 10-5
CAESAR II Version 2.1C Features (6/87)
Uniform and Independent support shock spectrum capability.
Force Spectrum Dynamic Analysis of Fluid Waterhammer.
Force Spectrum Dynamic Analysis of Relief Loads.
Force Spectrum Dynamic Analysis of Wind Gust Loads.
Fluid Mechanics Analysis of Gas or Liquid open vent relief system. Includes vent stack sizing, thrust, and pressure rise
computations.
NRC Dynamics Benchmarks for: NUREG/CR-1677, BNL-NUREG-51267, Vol. I, 1980; and NUREG/CR-1677, BNL-
NUREG-51267, Vol. II, 1985.
Dynamic Friction modeling based on static load case results.
Eleven (11) pre-defined shock spectra including all Reg. Guide 1.60 spectra and the El Centro North-South component
spectra.
Improved Harmonic Analysis including the effect of phased loading relationships. (Allows modeling of eccentrically
loaded rotating equipment.)
Improved dynamic output processor, includes user defined headings and user comments.
Animated static and dynamic solutions with structural members and hidden line volume plots.
Improved EIGENSOLVER many times faster than earlier algorithms, with automatic out-of-core solution mode.
Updated Static Analysis Load Case Processor.
New Friction Algorithm with interactive control during solution of nonlinear restraints.
Improved Output file handling of various solution methods.
Ability to abort any function at any time during a session using the <ESC> key.
New keydisk memory protection scheme.
Hardware/Software QA capability for analysis verification.
10-6 Update History
CAESAR II Version 2.2B Features (9/88)
Large Rotation SupportsAllows large rotation supports to be handled properly, by computing the support forces in all
three global directions. Rod and Chain hanger supports can be modeled now.
Nonlinear Out-of-Core SolverThis new solver increases the range of problems CAESAR II can solve by allowing
nonlinear solutions to be performed on the hard disk. This capability is necessary when a job is too large to be solved in
memory.
Friction ReportFriction is a non-conservative force, and CAESAR II treats it as such. The restraint reports will now
show restraint loads due to friction for each load case.
New External Interface HooksA new interface module will allow smooth interface to data conversion modules
between CAESAR II and other programs, such as AutoCAD. A new AutoCAD DXF interface is provided, and two thirds
of the part vendors have completed interfaces from their AutoCAD ISO packages to CAESAR II.
ASCII Editor - Due to an overwhelming need and subsequent lack of easy to use system editors, a stand alone ASCII
editor is being provided. This editor will enable users to easily modify files such as AUTOEXE.BAT, CONFIG.SYS,
and SETUP.CII.
2D XY Engineering Plotting ProgramA stand alone plotting program is provided to allow users to plot engineering
data, such as CAESAR II spectrum files. This program will plot any real data arranged in columns.
Valve & Flange DatabaseThe addition of a valve & flange database enables the user to define/select the specific rigid
element to be inserted into the piping system. The database is constructed to allow user additions and/or modifications.
Dynamic RestartThe most time consuming part of a dynamic analysis is the Eigensolution. This feature allows a job
to be restarted and use a previous Eigensolution.
WRC Updates latest edition (1979) of the WRC107 bulletin has been incorporated.
Input Title PageAn optional title page has been added to the input module of the program. Users can now define a
title page of up to 19 lines, which will be stored with the input.
Expansion Joint Rating ProgramThis stand alone program allows the user to compute the compression of each
expansion joint corrugation and the compression of the joint as a whole. These values can then be compared to
manufacturers recommendations for joint acceptance.
Chapter 10 Update History 10-7
CAESAR II Version 3.0 Features (4/90)
VGA Graphics support (on input)
Interactive (immediate) rotation of the input graphics image
Updated graphics user interface
Optional WRC 329 implementation of new stress intensification factors for intersections
Optional ASME Class 1 flexibility calculations for reduced intersections
Optional WRC 329 fixed to B31.1 and B31.3 piping code equations
Piping codes: B31.4, B31.8, ASME Sect III Class NC and ND, CAN Z184 and Z183, Swedish Power Methods 1 and 2,
BS806.
Updated SIF library to include welded joints and Bonney Forge fittings
New scrolling help screens
Editing list features, including rotate/duplicate of total or partial models
Updated WRC 107 table limit check
AISC member check
Wind load calculations on structural members
Additional stress equation control via the SETUP file
Numerical sensitivity checks in both the in-core and out-of-core solvers
Automatic expansion joint modeler using manufacturers database
Additional restraint types including bottomed-out spring hangers and bi-linear soil springs.
10-8 Update History
CAESAR II Version 3.1 Features (11/90)
Graphical Updates
Instantaneous center-of-rotation calculation
Element Highlight
Element Range
Rotating Equipment Report Updates
API 610 7th Edition Addition
SI/User Units
HEI Additions
WRC 107 Updates
Simplified input
WRC 297 stress calculations
Miscellaneous Modifications
Screen data presentation changes
Direct control jumping between executables
Increased number of allowed program designed hangers
Additional spring hanger design options
Database Updates include additional spring hanger tables
Soil Modeler for Buried Pipe
Chapter 10 Update History 10-9
CAESAR II Version 3.15 Features (9/91)
The installation program utilizes the file compression routines from PKWARE. This significantly reduces the number of
diskettes distributed and the time needed to install the CAESAR II package.
Flange Leakage and Stress Calculations
Elastic models of the annular plate, gasket and bolts predict the relative degrees of gasket deformation leading to a leaking
joint. Stress calculations in accordance with ASME Sect. VIII Div. 1 are also provided for comparison.
WRC 297 Local Stress Calculations
This bulletin supplements WRC 107, and in addition computes stresses in the nozzle as well as the vessel.
Stress Intensification Factor Scratchpad
The new module shows the effects of the various code options available in CAESAR II, and illustrates the relationship
between the various interpretations. WRC 329 SIF options are included. SIFs for stanchions on elbows are also computed.
Miscellaneous
A pen plotting program (PENPLT) plots up to 2500 element models (LARGE Includes) on the screen or on an HPGL
compatible hardware device.
The static output processor has been updated to support VGA graphics and to provide screen dumps to HP Laser Jet
Series II compatible printers.
Updated SYSCHK program now checks that SHARE is loaded when necessary. Missing coprocessor is also
immediately reported.
Updated PLTS now allows users to save labels, scaling information, and file names during plotting sessions.
Updated ROT (rotating equipment program) provides additional code interpretations for the HEI bulletin.
The BIGPRT (large job printing program) has been expanded to handle even larger jobs and to provide a local
element report.
As of Version 3.15, CAESAR II will utilize ESL devices to authorize access to the program. The ESLs are more stable
than the previously used keydisk and provide additional client information to the program. Additional information on
the ESLs can be found in the update pages for the User Manual.
Note: The first access of Version 3.15 will cause the ESL activation code to prompt for the keydisks (both unlimited and
limited). Both keydisks must be available to properly activate the ESL.
A printer setup program (PRSET) is provided to adjust the number of lines per logical page for dot matrix printers.
Users with page lengths longer than 11 inches will find this program very useful.
10-10 Update History
CAESAR II Version 3.16 Features (12/91)
The internal file maintenance utility has been completely rewritten. The new file handler provides the same capabilities
as the previous file handler but with faster response times. Additionally, the new file handler is compatible with disk
partitions larger than 32 Mbytes, and manipulates the data files created by Versions 3.xx of CAESAR II.
A configuration program has been added to CAESAR II to allow users to modify the SETUP.CII file from spreadsheets.
The configuration program also includes the standard COADE help interface to facilitate setting the directives.
The structural programs (C2S and AISC) have been revised to access either the 1977 AISC database or the 1989 AISC
database. Additionally, the AISC program has been updated to perform the unity checks (code compliance) using the
1989 code, which includes the methodology for checking single angles.
The equipment module (ROT) has been enhanced to handle vertical in-line pumps for API-610, 7th Edition.
The Stoomwezen 1989 (Dutch) piping code has been added.
Three additional spring hanger tables have been added (Basic Engineering, Capitol Pipe Supports, Piping Services
Company).
The editors found in the structural preprocessor, the ASCII file editor, and the piping preprocessor title page have been
modified to allow the insertion and deletion of single characters. Appropriate screen instructions are provided where
necessary.
An automatic loop closure command has been added to the piping preprocessor.
A jacketed pipe example has been included in the documentation. The input file for this example is included in the
EXAMPLES set on the distribution diskettes.
Updated moduli of elasticity for default CAESAR II materials based on 1990 code revisions.
Chapter 10 Update History 10-11
CAESAR II Version 3.17 Features (3/92)
Support of DOS environments now available in CAESAR II. This allows users to run the software from various
subdirectories on the hard disk, other than the installation directory.
Facilities have been provided to enable the user to modify the default colors used through out CAESAR II. Four
predefined sets of text colors are provided as well as the ability to modify whichever set is currently selected.
The Utilities menu has been expanded to include all of the secondary CAESAR II processors.
Help has been added for the Input graphics, the Pen Plot graphics, and WRC 107.
A new online error processor has been incorporated. This enables the software to provide the user with an explanation
of the cause of many fatal error messages, as opposed to the display of only the error number.
The file handler has been modified to allow the manual entry of a new job name.
The input piping preprocessor now includes a material number (21) for User Defined Materials.
The Static and Dynamic Output menus have been modified to allow the user to return directly to the input, or in the
case of the dynamics output, to invoke the animation module directly.
Graphics for flange selection and output have been added to the ASME Flange modules.
Input and output file sequencing are checked to aid in Quality Assurance, insuring that the current input file produced
the current output file. Input Echo reports are also possible from the static output processor.
10-12 Update History
CAESAR II Version 3.18 Features (9/92)
Codes and Databases
The Canadian codes Z183 and Z184 have been revised according to the 1990/1992 publications.
The Italian spring hanger manufacturer INOFLEX has been added.
The Database option of the configuration program now allows the user to set the desired Valve and Flange database.
Additionally a database excluding flanges (NOFLANGE) is included.
The Material Database used for the Flange Stress/Leakage module has been updated. The new database includes all
changes from the ASME Sect VIII, Division 1, A91 Addenda, the materials are listed in code order, and the number of
materials has increased from 450 to 1100.
The structural modules (C2S and AISC) have been updated to work with the German structural steel library, which is
also included.
Interfaces Added
A new neutral file interface is provided which allows a two way transfer of data between the CAESAR II input file and
an ASCII text file.
An interface is provided between Stoners LIQT program and the dynamic modules of CAESAR II. This interface
enables dynamic pipe forces from a time domain analysis to be used in the generation of a force spectrum.
Miscellaneous Changes
The static stress summary report has been modified so that the maximum code stress percent is reported, not the
maximum code stress.
A miscellaneous option has been added to the configuration program. This option allows various options, including
the specification of the ANSI, JIS, or DIN piping specifications.
Other options available from the Miscellaneous menu are:
Intro/Exit Screens (On/Off) - This option can be used to disable the display of the initial entry screen and the final exit
screen.
Yes/No Prompts (On/Off) - This option can be used to disable the yes/no/are_you_sure prompts.
Output Reports by Load Case (Yes/No) - By default, CAESAR II produces static output reports by load case. This option
can be used to generate the same reports by subject.
Displacement Report Node Sort (Yes/No) - This option can be used to disable the nodal sorting of the static
displacement report.
The file handler has been modified to enable directory and disk drive selection and logging. The initial display of the
file names can also be controlled by the user. This allows the user to set the sort order as well as the single/multi-
column display presentation.
A file verification routine has been added to check the installation of CAESAR II. This will aid in detecting program
corruption due to hard disk defects and viruses.
A new report has been added to the static output menu. This will enable users to obtain a local force/moment report
for the elements in the system.
A 32 bit version of the dynamic summation module is provided for large dynamic analysis. Note, this module requires
at least a 386 processor.
The animation module has been modified to provide hard copy output of the mode shapes.
Chapter 10 Update History 10-13
CAESAR II Version 3.19 Features (3/93)
Batch Stream ProcessorA new processor has been included which will allow multiple jobs (up to 12) to be run in
series, without user intervention. The jobs can be static analysis, dynamic analysis, or both.
Expansion Joint DatabaseThe Pathway Bellows expansion joint database has been updated. The new database
includes two additional pressure classes and diameters out to 144 inches.
A new expansion joint database from RM Engineered Products has been added for this release.
Input EchoThe input echo processor has been modified so that the input echo precedes the output data. Additionally,
the intermediate data generated by the error checker now appears in this listing.
B31GThe B31G criteria for the remaining strength of corroded pipelines has been incorporated. This module
includes the original B31G criteria as well as several of the modified methods discussed in the Battelle project.
Output ProcessorA new report has been added to the output processor which generates a Restraint Summary report.
This summary details all the loads for all selected load cases for each restraint in the model.
Thermal BowingThe effects of thermal bowing on horizontal pipes can be analyzed. By specifying the thermal
gradient between the bottom and the top of the pipe, CAESAR II will compute the loads induced and include them with
the thermal loads.
32 Bit ModulesAll of the dynamic modules have been moved from the 16 bit mode to the 32 bit mode. Additionally,
the animation program now supports EGA and VGA display modes.
Title Page TemplateA user-configurable ASCII text file can now be used as a title page template.
Interface UpdatesThe CAESAR II data matrix interface and the Autoplant interface have both been updated to utilize
the currently active units file. The ComputerVision interface has been updated to handle tube type piping.
Expansion Joint RatingThe expansion joint rating module, ERATE, has been moved into the Miscellaneous
Module, facilitating input via the standard spreadsheets.
Refractory LiningThe computation modules of CAESAR II have been modified to accept a negative value of
insulation thickness. If a negative thickness is encountered, the program will assume the insulation is refractory lining
(inside the pipe).
Minimum Required ThicknessThe piping error checker now makes the minimum required thickness computation
according to B31.1, 104.1. This information is reported for each pipe in the listing of intermediate data (See item 3
above).
Spring Hanger TablesThe E. Myatt & Co. spring hanger table has been added.
ESL UpdatesAll of the code used to access the ESLs has been updated to allow access to the 50 and 66 Mhz CPUs.
Missing MassThe dynamics modules can consider missing mass effects in the spectrum solutions.
Seismic Anchor MovementsThe dynamics modules will allow the specification of seismic anchor movements for
independent support motion analysis.
RCC-MThe French piping code RCC-M, Section C has been incorporated.
LanguagesThe input and dynamic output supports English, French, and Spanish language headings. Language
dependent files can be activated with the appropriate command line switch on the INSTALL directive. For example,
INSTALL /S will install any Spanish specific files.
PCX FilesAll of the graphics modules have been modified to allow the images to be saved to disk files in PCX
format. This will enable these images to be brought into word processing and desktop publishing systems.
10-14 Update History
CAESAR II Version 3.20 Features (10/93)
A completely new documentation set accompanies this release. This documentation consists of: a User Guide, an
Applications Guide, and a Technical Reference Guide.
The static in-core and out-of-core solvers have been converted to run in 32 bit protect mode utilizing extended memory.
Solution times for large jobs have been cut by an order of magnitude.
The Static Output processor has been converted to run in 32 bit protect mode utilizing extended memory.
Both the Static and Dynamic Output processors now have the capability to generate ASCII disk files on any drive or
directory (using the COADE file manager) on the computer. Additionally, a table of contents summarizing the output is
generated for printer and disk devices.
The Dynamic Output processor now includes titles and page numbers (similar to statics), and provides input echo (both
system and dynamic) abilities.
Modal time history analysis has been added. This includes output report review and animated response review.
Standard spectrum analysis now include modal components for displacements. Additionally displacement information
is now available for static-dynamic combinations.
The Included Mass Report has been clarified and modified to include the active mass in each of the global directions.
The percent of the force included/added is now based on a vector sum rather than an absolute sum.
The ZPA used in the missing force correction can now be controlled via the configuration file. The user can specify that
the ZPA be based on the last extracted mode or the last spectrum value.
The static load case array space has been increased by a factor of 5, allowing more flexibility in static load case setup.
API 650 nozzle flexibilities, according to the ninth edition, July 1993.
Checks for allowable loads on Fired Heater Tubes according to API-560 have been added.
As an option, users can consider the effects of pressure stiffening on straight pipes.
Three additional spring hanger tables: Sinopec (China), BHEL (India), and Flexider (Italy).
The Australian structural steel shape database has been added.
The ASME material database has been updated to reflect the 1992 Code addendum.
The printer testing routines have been completely rewritten. Additionally, output can be directed to any LPT port.
The ability to configure the printer, either dot matrix or laser jet. This is implemented via a text file containing the
printer formatting codes, which the user is free to modify.
Password protection for input data files, to prevent modification of completed projects.
All of the screens in the piping preprocessor (except for the main spreadsheet) are now supported in Spanish and
French.
Input/Output file time/date sequencing checks have been added to the dynamics modules.
The break command in the piping input processor has been modified to accept input in feet-inch units instead of only
feet. This should allow compound entries in any units system.
Chapter 10 Update History 10-15
CAESAR II Version 3.21 Changes and Enhancements (7/94)
Most of the CAESAR II executable modules have been converted from Microsoft 16 bit FORTRAN to WATCOM 32 bit
FORTRAN. This has reduced the low DOS RAM requirements of the program from 577k to 475k.
The modules converted to 32 bit operation for Version 3.21 are summarized below:
Static Stress Computation Module (1)
Piping, Buried & Structural Steel Input Modules (3)
Piping Error Checker (1)
Load Case & Dynamic Input Module (1)
All CAD interfaces (8)
Neutral File interfaces (2)
The software now supports an ESL from a new vendor. This provides CAESAR II with full networking abilities. The program
first checks for a local ESL (from either vendor), then for a network ESL.
Toward the support for network operations, the data files which are not job specific are now assumed to be located in a
SYSTEM subdirectory underneath the CAESAR II installation directory. These data files include: the input listing formatting
files (*.INP), the accounting data files, the printer formatting file, the file handler template file, and the various header files.
The common factor among all of these files is that they are specific to a company installation, not a particular data directory.
Up until Version 3.21, these data files were manipulated by the program (or sometimes directly by the user) in the
installation directory. However, many network installations write protect their installation directories, making
modifications to these files impossible. We have therefore placed these files in a SYSTEM subdirectory to which users
should be given complete access.
Note: CAESAR II Version 3.21 will be capable of running on a local machine (with either vendors local ESL) or on a
network (with the network ESL). The changes made to the software enable the same version to be run under these various
configurations.
Added additional spring hanger manufacturer has been added, Carpenter & Paterson, UK.
The UBC (Uniform Building Code) earthquake spectra have been added.
The B31.5 piping code has been added.
The piping code addenda have been reviewed and any necessary changes made to the software. The addenda include
revisions for: ASCE #7, B31.1, B31.8, ASME NC, and ASME ND.
The SIF scratch-pad from the Miscellaneous processor (Option C of the Main Menu) has been incorporated into the
piping preprocessor. This processor includes all of the supported piping codes (not just B31.1 and B31.3 as before) and
all of the fittings. Additionally, any changes made to the scratch-pad data can optionally be transferred directly to the
main CAESAR II data spreadsheets.
Additional changes to the input piping preprocessor include the following:
problem size is now dependent on the amount of free extended memory - the old limit of 400 elements is now upwards of
8,000 elements
graphics menus automatically turned off for hard copies
optional node number display for supports, anchors, hangers, and nozzles
function key map shown on main spreadsheet
auxiliary input spreadsheets support help
10-16 Update History
The accounting system has been completely rewritten. This provides a more streamlined interface. Additionally,
accounting statistics are now recorded from the stress computation modules (previous versions only recorded the actual
matrix decomposition times).
The API-617 and NEMA-SM23 reports have been overhauled so that the code compliance when using non-English
units systems is consistent.
The new Flange Rigidity factor from ASME Section VIII has been added.
A new loader (C2.EXE) has replaced the original one (C2.COM). This new loader performs initial startup checks, with
diagnostic reporting if necessary, and enables error processing from the Main Menu.
The configuration program has been modified to track changes. Users attempting to [Esc] out after making changes are
warned that the changes will not be saved.
A graphics viewer has been added to the file manager. This enables rapid model plotting directly from the file manager
of the Main Menu.
Additional directives are available to disable the generation of the Table of Contents page, and disable the display of
the spreadsheet function key mapping.
Chapter 10 Update History 10-17
CAESAR II Version 3.22 Changes & Enhancements (4/95)
The following enhancements and additions have been added to CAESAR II for the Version 3.22 release. Any Technical
Changes made, which could affect the computed results, are listed below.
The Harmonic solver has been updated to provide damping. Harmonic analysis can now include or exclude damping
as the user deems necessary.
The following codes have been reviewed (and any necessary changes made) for compliance to the latest editions:
B31.1, B31.3, B31.4, B31.5, B31.8, NC, ND, and BS-806.
The following additional piping codes have been added: RCCM-D, CODETI, and TBK 5-6.
Center of Gravity calculations have been added, with results displayed in the error checker.
A Bill of Materials report has been added.
Yield criterion stresses can be computed as either Von Mises or as 3D Maximum Shear Stress intensity.
Hoop Stress can be computed based on Outer Diameter, Inner Diameter, Mean Diameter, or Lames equation.
The spring hanger design spreadsheet has been modified to default to a 25% load variation. In addition, the actual
hanger load variation now appears in the hanger output reports.
A new command (WIND) has been added to the structural steel preprocessor. This allows selective wind loading on an
element by element basis.
A new key-combination Alt-D is available in the input processor to compute the distance between two nodes.
User specified coordinates for up to 30 nodes are saved in the input file.
The input title page has been expanded from 19 to 60 lines.
Automatic node numbering abilities have been added to the spreadsheets of the main piping input module
Expansion Joint databases from IWK (Germany) are provided.
Expansion Joint database from Senior Flexonics is provided.
MISC converted to 32 bit operations. This module provides the SIF, Flange, WRC297, B31G, and expansion joint
rating computations.
ROT converted to 32 bit operations. This module provides the equipment calculations for NEMA, API, and HEI.
General revisions made for more consistent input screens and help messages.
A new report option (in static output) is available to review the miscellaneous computations made by the error
checker. This report includes: SIFs and flexibility factors, pipe properties, nozzle flexibility data, wind data, CG data,
and the bill of materials report.
The Intergraph Interface has been improved. The interface now transfers the temperature/pressure pairs. Additionally, if
a material mapping file is present, material data can be set correctly by CAESAR II.
The CADPIPE Interface has been updated in accordance with CADPIPE Version 4.0.
The Restraint Summary in the static output processor has been modified to include the translational displacements of
the restrained nodes.
The output processors (static and dynamic) have been modified to allow users to change the name of the disk output file
if desired. Additionally, modifications have been made so that only a single output device can be enabled.
All language files have been translated into German. Use INSTALL /G to acquire the German files.
A new control F8 at the output menu level allows switching jobs without returning to the Main Menu.
10-18 Update History
CAESAR II Version 3.23 Changes (3/96)
The following items have been completed for the 3.23 release:
Mouse support has been added to most modules.
The German piping code, FBDR, has been added.
Major improvements to FRP (fiber reinforced plastic) stress calculations. This includes the BS 7159 code and
guidelines set forth by FRP manufacturers.
A bi-directional link to CADWorx/Plant (COADEs Piping CAD system) has been added.
The WRC107 module has been redesigned to incorporate multiple load cases and perform the ASME Division 2 Stress
Intensity Summation, all in one step.
An interface to Sunrise Systems PIPENET program has been developed.
The South African structural steel tables are being added.
Two new spring hanger manufacturers tables have been added; Comet (UK), and Witzenmann (Germany).
Two new commands have been added to the structural preprocessor: UNIT, and GLOAD.
The CADPIPE interface has been updated to comply with the new release (Version 4.1) of CADPIPE.
Additional modifications have been made to the Intergraph interface.
The low DOS RAM requirement has been reduced to 420 Kbytes.
The equipment module has been updated to reflect the 1995 edition of API-617.
The following U.S. piping codes have been updated according to recent editions: B31.3 (1995)
Chapter 10 Update History 10-19
CAESAR II Version 3.24 Changes & Enhancements (3/97)
The following items have been added or modified for the 3.24 release:
Multiple (3) displacement/force/uniform load vectors have been added. Note that these load cases, called D1/D2/D3
and F1/F2/F3, may be toggled on the input plot by continuing to press F3 and F5 (displacements cycle through D1, D2,
D3, and then off). The naming of these load cases has also required the renaming of the CAESAR II load combination
terms D1, F1, S1, etc. must now be called DS1, FR1, and ST1. Note that all hanger loads and cold spring forces
(from materials 18 and 19) are still lumped into load case F1, for consistency with previous versions of CAESAR II.
A material database for piping properties and allowable stresses for many of the piping codes supported by CAESAR II
has been implemented. This is invoked by pressing [ALT-M] on the main CAESAR II input spreadsheet (also at the list
option and on the WRC 297 nozzle flexibility spreadsheet). After bringing up the list of materials, a material name can
be typed in; matching records are then displayed for selection. Allowable stresses are updated automatically whenever
temperatures, materials, and/or piping codes change.
Database management is provided from the Utilities option of the main menu. Users may edit COADE provided
materials or add their own. Material parameters may be provided for code 0 (represents generic values for any non-
specified code) or for specific codes. It is recommended (due to future implementation plans) that metals be assigned
identification numbers between 100 and 699, while FRP materials receive numbers between 700 and 999. Note that
selection of FRP materials from the material database will not currently activate the orthotropic material model in
CAESAR II. This must still be done through the use of material 20 (see item 6 concerning this below).
Eight-character job names are now supported (input files are identified by extension ._A, output files by extension ._P,
._S, etc.). Existing files are automatically recognized and converted to their new format. (See related item 16 below.)
Modifications have been made to allow multiple users working from the same network data directory via the
environment variable COADE_USER. This environment variable should be set to a unique 3 character combination
(i.e., the users initials) for each user working in the common directory. Implementation can be done by adding to the
users AUTOEXEC.BAT file a line such as: SET COADE_USER=TVL
CAESAR IIs Valve and Flange database now incorporates data files from CADWorx/Plant. This change provides four
advantages:
Component weights and lengths are more accurate, as well as traceable to specific catalogs, standards, etc.
Weights and lengths are provided for more components than were previously available in the CRANE or GENERIC
databases.
Since CADWorx/Plant data files are text files, users may easily edit or add components.
If the user also has CADWorx/Plant on their machine, the two programs will share the same data files and project specs,
enhancing the performance of the bi-directional interface. Gaskets are included for flanged items, so a better fit is
provided between the CADWorx/Plant and CAESAR II models.
10-20 Update History
The user may now set default values for FRP (material 20) parameters via the configuration/setup. These default
parameters may be read automatically from manufacturers data files by toggling through the list of available files, and
then pressing [ALT-U] (for Update) on the selected vendor file. Vendor files are recognized by their .FRP extensions;
since these are text files, users may create them easily themselves, or vendors may distribute them to their customers.
The UKOOA (United Kingdom Offshore Operators Association) piping code for FRP piping has been added.
The Z183 and Z184 piping codes have been replaced with the Z662 code, which has been expanded to consider
calculation of stresses in restrained piping.
The ASCE #7 wind code has been updated to the 1995 edition.
The API-610 code in the equipment module has been updated to the 8th edition.
ASME Section VIII Division 2 stress indices and WRC-107 SIF (kn, kb) values have been incorporated into the WRC-
107 module.
The Relief Load Synthesis dynamics module now supports metric (or custom) units.
A number of configuration file default values have been revised in order to improve calculational results or program
performance:
Changed From To
BEND_LENGTH_ATTACHMENT= 5.0 1.0
BEND_AXIAL_SHAPE = NO YES
FRICT_STIFF = 50000 1.0E6
FRICT_NORM_FORCE_VAR = 25 15
FRICT_ANGLE_VAR = 30 15
VALVE_&_FLANGE = GENERIC CADWORX
Four new directives added to the configuration file.
SYSTEM_DIRECTORY_NAMEUser defined, defaults to SYSTEM (note user may now maintain multiple system
directories for different projects)
UNITS_FILE_NAMEUser selected from list (note current units are now set through the configuration/setup, not through
the units option of the main menu)
BS_7159_PRESSURE_STIFFENINGDesign strain or Actual Pressure
FRP_PROPERTY_DATA_FILEUser selected from list
The configuration file can also be password protected in the Installation Directory. This prevents modification of all
Computation and Stress Control directives. Subsequent use of the configuration module prevents modification of these
directives, unless the password is known. Colors, printer settings, etc. may still be changed by users without the
password.
CAESAR II has been modified to accept an optional job name (including full drive and path data) as an argument; the
program switches to the appropriate drive and directory, opens the specified job, and goes into input (bypassing the
Main Menu). This allows the definition of ._A files as CAESAR II input files (under Windows 95) and subsequent
double clicking on the file name in a Windows/95 explorer window to start the input processor on the picked job file.
This also allows CAESAR II to be spawned from other programs, right into a job.
Modifications to CAD interfaces: Intergraph and CADPIPE.
All necessary routines have been checked (and modified where appropriate) to address the Year 2000 issue.
A Korean structural steel shape library has been added.
A new spring hanger table has been added (SARAFTHI).
PD-5500 nozzle flexibilities have been incorporated to complement the WRC-297 and API 650 nozzle connections.
Chapter 10 Update History 10-21
CAESAR II Version 4.00 Changes and Enhancements (1/98)
The CAESAR II Version 4.00 release is a major program rewrite making it compatible with Windows 95/NT (version 4.0)
operating systems. Minimal functionality enhancements were included in order to make CAESAR II input files
interchangeable between Version 4.00 and CAESAR II Version 3.24, the last DOS-based version. Specific new features
include:
Simultaneous review of graphics and spreadsheet.
Addition of rendering and wireframe graphics in plot mode.
The ability to turn off subsequent occurrences of an error type in the piping error checker.
The ability to extract loads directly from a piping output file for inclusion in the WRC 107 and rotating equipment
modules.
Addition of bend mid-point modes (indicated by angle M) which allow the user to designate the mid-point of the
bend without knowing the included angle.
Ability to review 132-column reports on screen.
10-22 Update History
CAESAR II Version 4.10 Changes and Enhancements (1/99)
CAESAR II version 4.10 changes and enhancements (1/99) include
9 temperatures, 9 pressures, 9 displacement sets, and 9 force/moment sets
Finalization of TD/12 piping code
Fatigue capabilities including cumulative damage
Increase in number of load cases to 99
Reactivation of the input LIST facilities
Printing capabilities for graphical renderings
Saving graphics images to BMP files
Online User and Quick Reference Guide in PDF format
Update of piping codes (CODETI, NC, ND, B31.1, B31.3)
Addition of results filters to output reports
Update of Technical Reference Manual to reflect Windows version of CAESAR II
Variability of mill tolerance on an element-by-element basis
Chapter 10 Update History 10-23
CAESAR II Version 4.20 Changes and Enhancements (2/00)
CAESAR II version 4.20 changes and enhancements (2/00) include
New Input Graphics - utilizes a true 3D library, enabling graphic element selection
New "local coordinate" element input/specification
Completely revised material database, including Code updates.
Optional static output in ODBC compliant database format.
Hydrodynamic loading for offshore applications. This includes the Airy, Stokes 5th, and Stream Function wave
theories, as well as Linear and Power Law current profiles.
Wind analysis expanded to handle up to 4 wind load cases
New piping codes: B31.4 Chapter IX, B31.8 Chapter VIII, and DNV (ASD)
A wave scratchpad - see the recommended theory graphically, or plot the particle data for the specified wave.
Updated piping codes: B31.1, B31.3, B31.4, ASME NC, and ASME ND
Automatic Dynamic DLF Plotting
Witzenmann expansion joint databases
As a result of the merger between Senior Flexonics and Pathway Bellows, a new expansion joint database replaces the
two previous individual databases.
A new spring hanger vendor (Myricks) is provided.
PCF Interface
10-24 Update History
CAESAR II Version 4.30 Changes and Enhancements (3/01)
New Static Load Case Builder / Editor. Allows multiplication factors on load components plus additional combination
methods (SRSS, Algebraic, ABS, Min, Max, Signed Min, Signed Max, and Scalar).
Z-Up: Build or review models with "Z" as the vertical axis instead of "Y". Switch between "Y" and "Z" up on the fly.
New "undo/redo" ability in the piping input module.
Piping input can be sent to ODBC database.
A new "data export" wizard is provided to selectively target input or output data for ODBC export.
All modules support optional output directly to MS-Word.
Updated piping codes: B31.1, B31.3, B31.4, ASME NC, and ASME ND.
User Control over the "auto-save" feature implemented.
Improvements to the 3D graphics (job specific configuration, additional data display).
Added graphics to the WRC 107 Module to show loads and orientation.
Added a new "Code Compliance" report to the static output processor.
Spring hanger design expanded from 3 to 9 operating cases.
Chapter 10 Update History 10-25
CAESAR II Version 4.40 Changes and Enhancements (5/02)
Revised piping codes: B31.3, B31.4, B31.5, B31.8, ASME NC, ASME ND
Added the B31.11 piping code.
Added an alpha-numeric node label option to the piping input module
Expanded Static Load case options: (1) added load components H, CS, HP, and WW (hanger loads, cold spring, hydro
pressure, and weight filled with water, respectively), (2) added HYDRO stress type, (3) added option to set snubber and
hanger status on a load case basis, (4) provided ability to scale friction factor on a load case basis.
Added automatic generation of a hydrotest load case (WW+HP, HYD stress type, and spring hangers locked), triggered
by the presence of a non-zero HP.
Updated the 3D input graphics, as well as partial implementation in the static output processor (including the "Element
Viewer").
Updated the spring hanger design algorithm to provide the option to iterate the "Operating for Hanger Travel" load case
to include the stiffness of the selected hanger.
Added new configuration options for ambient temperature, default friction coefficient (if nonzero, automatically gets
applied to new translational restraints), liberal stress allowable, stress stiffening, and Bourdon settings, as well as how
to handle B16.9 welding tee and sweepolet SIFs in B31.3.
Added two new spring manufacturers' tables Pipe Supports USA and Quality Pipe Supports.
Added the ability to define the flexibility factor on bends.
Included piping and structural files now support long file names, may be located in any directory path, and the number
of included structural files has been expanded from 10 to 20.
Results of the Hanger Design Cases are now optionally viewable in the Static Output Processor (set status to "KEEP" in
the Load Case Options).
Added the ability to filter static Restraint reports by CNODE status.
Added a new "warning report" to the static output.
Added a "dirty flag" to the piping input preprocessor and the configuration modules. Attempting to exit these
processors without saving changes produces a warning message.
Added the ability to detect the differences between material data in the input file and that in the material database
(including missing "user materials"). This feature offers the user the opportunity to use the original data.
Reviewed/updated the "minimum wall" computation for all piping codes for straight pipe.
Added a field for specifying Marine Growth Density to the Wind/Wave dialog.
Updated API-661 to 4th Edition.
Added the ability to save static load case data without running the job.
10-26 Update History
CAESAR II Version 4.50 Changes and Enhancements (11/03)
CAESAR II Version 4.50 contains some major new features as listed in the table below.
Revised material database for B31.1 A2001 changes
Added Reducer element.
Improved user interaction and error reporting in static load case editor.
Improved graphics changes include:
- A walk-through option is available.
- The static output processor can now produce colored stress plots of the piping system.
- A graphical find (zoom to) option has been added.
- Instant use of graphics, even before drawing is completed.
- Recitable restraint/hanger symbols
Added Spectrum wizard for the generation of earthquake and relief valve spectra.
Revised codes: B31.1, B31.4, ASME NC, ASME ND, IGE/TD/12, API-610.
Included additional FRP data files
The static output processor remembers all user settings (filters, labels, and report size)
Added dynamic help system for piping & structural input and configuration.
Added automatic acquisition of website software updates.
Combined WRC-107/297 module for local stress calculations.
Redesigned the structural steel interface for easier operation.
Implemented a "new job wizard" for the creation of structural steel input models.
Modified to allow multiple instances of CAESAR II to run
Implemented "Load Case Template" for recommending static load cases.
Modified to allow access to the output for expired date or run limited ESL
Chapter 10 Update History 10-27
CAESAR II Version 5.00 Changes and Enhancements (11/05)
CAESAR II Version 5.00 contains some major new features as listed below.
Added the following new piping codes: EN-13480, GPTC/192, Z662 Ch 11
Revised due to code changes the following piping codes: B31.1, B31.3, B31.5, B31.8, B31.11, ASME NC, ASME
ND, CODETI, TBK 5-6.
Updated API-610 codes and standards
Added Ameron Bondstrand, and Conely FRP Pipe Specification files.
Added Binder (UK) and PiHASA (Spain) Spring Hanger tables.
Added Structural Steel databases from India and Japan.
Renamed all references to Grinnell to Anvil.
Added the capability to perform dynamic analysis optionally using a consistent mass matrix. This obviates the need to
re-mesh the model for better mass distribution.
Added the capability to perform an analysis using the hot material elastic modulus.
Enhanced the static output processor to provide users with the ability to create custom, reusable reports.
Revised he piping input processor to provide a combined view showing both the graphics and the spreadsheet. The
new piping input processor has integrated the Piping Error Checker, and access to the configuration module has been
provided. For debugging and problem solving, relevant sections of the spreadsheet can be torn off and placed on the
graphics pane, allowing the spreadsheet to be hidden for larger graphics display. Additionally, sections of the model
can be graphically selected and then modified.
Updated the Intergraph and PCF interfaces.
Added an Isogen export facility allowing the creation of Isogen stress isometrics.
10-28 Update History
CAESAR II Version 5.10 Changes and Enhancements ( 9/07)
This list details the new or changed capabilities and features of CAESAR II Version 5.10.
Added flange rating evaluation per B16.5 and NC-3658.
Graphics Improvements:
Improved graphics rendering speed proved by 20% to 50% depending on the job.
Added additional controls to view corrosion and densities.
Added the ability to import an Autocad (CADWorx) model directly into the piping input, to provide visualization of
supporting steel, vessels and other equipment.
Static Output Processor Improvements:
Reduced report generation times by 70% or better
Added Presentation in tabbed window to allow viewing multiple reports, and immediate switching between reports.
Added ability to select Individual items from Miscellaneous Report
Added ability to zoom reports and individually direct to an output device using a context menu
Added ability to import and export custom report templates.
Static Load Case Editor Enhancements
Added In-Line Flange Evaluation at the load case level.
Added the ability to alter the occasional load multiplier on a per load case basis.
Added the ability to import static load case data from different jobs
Added the ability to copy wind and wave vectors.
Added user control over whether or not insulation should be considered in hydro test cases.
Added PD-8010 Part 1 and Part 2 piping code.
Revised the following piping codes due to code changes: B31.1, B31.3, B31.4, Z662, EN-13480
Added support for B31.3 Section 319.2.3(c), allowing axial stress to be included in the Expansion Code Stress.
Revised API-661 to 6th Edition.
Revised Wind and Seismic load calculations to ASCE #7 2005.
Added a number of European materials to the material database.
Updated stainless steel pipe specification data per B36.19M.
Updated DIN pipe size specification to comply with EN-10220 (seamless) instead of DIN-2458 (welded).
Added Chinese structural steel and expansion joint databases.
Added spring hanger data from Gradior Power, (Czech Republic).
Updated the flange material database per ASME Sect VIII Div 1, 2007 Edition.
Updated the Inoflex Spring Hanger data.
Index
<
<Directive Data> 5-26
3
3-D space 3-5
A
A1 - Partial Factor for Temperature 3-90
A2 - Partial Factor for Chemical Resistance 3-91
A3 - Partial Factor for Cyclic Service 3-91
Absolute
Expansion Load 6-5
Method 5-58
Absolute Method 5-61
Acceleration
Factor 5-56
Vector 5-41, 5-48
Access 8-81
Access Protected Data 2-30
Account Number 7-1
Accounting 7-2
Menu 7-1
Summary reports 7-1
System 7-1
Accounting file 7-6
Accounting file structure 7-6
Accounting File Structure 7-6
Acoustic
Flow problems 5-41
Resonances 5-67
Shock 5-69
Vibration 5-3
Activate
Accounting Tab 7-1
Activate Bourdon Effects 3-119
Actual Pressure 2-12
Add 4-10
Add F/A in stresses 2-23
Add F/A in Stresses 2-23
Add torsion in sl stress 2-23
Add Torsion in SL Stress 2-23
Added mass coefficient 6-29
Added Mass Coefficient, Ca 3-64
Advanced Options 2-16
Advanced parameters 5-64
Advanced Parameters 5-64
Airy Wave Theory 6-25
Airy Wave Theory Implementation 6-27
AIRY Wave Theory Implementation 6-27
AISC 1977 Database 4-50, 4-51, 4-52, 4-53
AISC 1989 Database 4-56, 4-57, 4-58, 4-59, 4-60, 4-
61
al(0
1) Long Term Axial Stress at 0
1 Stress Ratio 3-88
al(1
1) Long Term Axial Stress at 1
1 Stress Ratio 3-88
al(2
1) Long Term Axial Stress at 2
1 Stress Ratio 3-89
All Cases Corroded 2-24
Allow short range springs 3-49
Allow Short Range Springs 3-49, 3-115
Allow User's SIF at Bend 2-24
Allowable
Load variation 3-47
Allowable load variation (%) 3-47
Allowable Load Variation (%) 3-47, 3-115
Allowable Stress 7-17
Allowable stressAllowable 3-71, 3-73, 3-75, 6-36, 6-
86, 7-17
Stress 7-17
Allowable Stresses 3-71
Allowed Intersection / Joint Types 3-98
Alpha 3-22, 4-14
ALPHA 4-14
Alpha tolerance 3-8
Alpha Tolerance 2-3
Alpha toleranceAlpha tolerance 2-3
Alternating pressure 5-67
Ambient temperature 3-84, 3-121
Ambient Temperature 2-6, 3-121
Analysis Type (Harmonic/Spectrum/Modes/Time-
History) 5-40
Analysis type (harmonic/spectrum/modes/time-
history)Analysis
Type 5-40
Anchor 3-40
Anchor Movement (Earthquake Only) 5-20
Anchors 2-17, 3-40
Angle 3-14, 4-29
ANGLE 4-2, 4-29, 4-30
AngleAngle 4-30
Angular
Forcing frequency 5-41
Frequency 5-44, 5-48
Stiffness 3-109
ANSI
A58.1 6-20, 6-22
B36.10 3-7
B36.10 Steel Pipe Numbers 3-7
B36.19 3-7
Nominal Pipe OD 3-5
API 650 Delta T 3-57
API 650 Fluid Height 3-57
API 650 Nozzle Height 3-57
2 Index
API 650 NOZZLES 3-56
API 650 Reinforcing 1 or 2 3-57
API 650 Specific Gravity 3-57
API-650
Delta t 3-57
Fluid height 3-57
Nozzle height 3-57
Nozzles 3-56
Reinforcing 1 or 2 3-57
Specific gravity 3-57
Tank coefficient of thermal expansion 3-57
Tank diameter 3-57
Tank modulus of elasticity 3-57
Tank wall thickness 3-57
API-650 Tank Coefficient of Thermal Expansion 3-57
API-650 Tank Diameter 3-57
API-650 Tank Modulus of Elasticity 3-57
API-650 Tank Wall Thickness 3-57
Append Reruns to Existing Data 2-8
Applicable Piping Code 7-16
Applicable Wave Theory Determination 6-26
Applications - Utilizing Global and Local Coordinates
6-123
Apply B31.8 Note 2 2-25
Archiving 9-16
Area 4-16
ASCE Example Problem 3-66
ASCE Static Seismic Wizard 3-65
ASME
Sect. VIII Division 2 6-36
Section VIII division 2 - elastic analysis of nozzle
6-36
ASME III Subsections NC and ND 6-92
ASME NC/ND 3673.2(b)-1 Note 3 3-28
ASME NC-3658.3 Calculation for B16.5 Flanged
Joints with High Strength Bolting Method 6-
3
ASME Section VIII Division 2 - Elastic Analysis of
Nozzle 6-36
Assume Standard Schedule 8-56
At Node 3-135
Australian 1990 database 4-64
Australian 1990 Database 4-64
Auto Node Number Increment 2-14
Auto node number incrementAuto node number
increment 2-14
Autosave Time Interval 2-20
Auxiliary 9-12
Data 3-130
Element data 8-60
Processors 1-1
Auxiliary Element Data 8-60
Auxiliary fields
Boundary conditions 3-39
Component information 3-13
Imposed loads 3-61
Piping code data 3-71
Auxiliary Fields - Boundary Conditions 3-39
Auxiliary Fields - Component Information 3-13
Auxiliary Fields - Imposed Loads 3-61
Auxiliary Fields - Piping Code Data 3-71
Available commands 3-93
Available Commands 3-93
Available Expansion Joint End-Types 3-111
Available space 3-47, 3-111
Available Space 3-111
Axial
Elastic modulus 2-11
Modulus 3-10
Restraint 3-84
Shape function 2-3
Stiffness 6-7
Axial Modulus of Elasticity 2-11
Axial strain
Strain
Hoop stress 2-11, 6-94
Axial Strain
Hoop Stress (Ea/Eh*Vh/a) 2-11
Axis Orientation Vertical 4-2, 4-12
B
B2 3-27
B31.1 6-84
B31.1 reduced z fix 2-24
B31.1 Reduced Z Fix 2-24
B31.11 6-91
B31.3 6-86
B31.3 Paragraph 319.2.3(c) 2-24
B31.3 sustained case SIF factor 2-24
B31.3 Sustained SIF Multiplier 2-24
B31.3 Welding and Contour Insert Tees Meet B16.9
2-25
B31.3 Welding and Contour Tees Meet B16.9 2-25
B31.4 6-87
B31.4 Chapter IX 6-88
B31.5 6-88
B31.8 6-89
B31.8 Chapter VIII 6-90
Background Colors 2-16
Bandwidth optimizer 3-128
Bandwidth Optimizer Options 3-128
Base hoop stress 2-25
Base Hoop Stress On ( ID/OD/Mean/Lam) 2-25
Base pattern 4-25
Base Stress/Flexibility on (IGE/TD/12 code only) 3-
121
Basic element data 8-58
Basic Element Data 8-58
Basic loading case 6-5
Basic material yield strength 3-82
Index 3
Batch mode 7-7
Batch stream processing 7-7
Batch Stream Processing 7-7
Beams 4-34
Fix 4-34
Free 4-34
BEAMS 4-2, 4-34
Bellows 3-113, 6-7
Allowed torsion 3-110
Application notes 3-110
Bellows Application Notes 3-110
Bellows Stiffness Properties 3-20
Bend Axial Shape 2-3
Bend Cost Factor 3-136
bend flexibilty factor 3-16
Bend Length Attachment Percent 2-14
Bend Radius 3-103
Bend SIF Scratchpad 3-103
Bend Type/Laminate Type 3-103
Bending stiffness 6-7
Bends 3-13
Axial Shape Bends
Axial shape 2-3
Curvature 2-15
Length attachment percent Bends
Length attachment percent 2-14
Miter 3-14
Node 3-29
Radius 3-14
Bi-directional data transfer link 8-4
Block operations 3-130, 3-131
Block Operations 3-131
Bolt Area (Ab) 3-19
Bonney forge sweepolets 3-25
Bottom 2-16
Bounding Box Visibility 2-18
Bourdon Pressure 3-119
Boxh 4-16
BOXH 4-16
Boxw 4-16
BOXW 4-16
Braces 4-36
Fix 4-36
Free 4-36
BRACES 4-2, 4-36
Branch
Connections 3-25
Flexibilities 6-12
Pipe spreadsheet 3-29
Stress intensification 3-29
Branch error 3-119
Branch Error and Coordinate Prompts 3-119
Branch Pipe Outside Diameter 3-103
Branch Pipe Wall Thickness 3-103
Break 3-93
Break command 3-93
Break Command 3-93
Browse 8-23, 8-56
BS 7159 3-10, 3-25, 6-105
BS 7159 pressure stiffening 2-12
BS 7159 Pressure Stiffening 2-12
BS806 6-97
Building elements
Elem, efill, egen, edim, Building elements 4-22
Building Elements - ELEM, EFILL, EGEN, EDIM 4-
22
Building Spectrum / Time History Load Cases 5-19
Building spectrum load cases 5-19
Buoyancy force 6-26
Butt weld 3-25, 3-87
Butt-welded tees 3-25
BY 4-20
C
CAD Interfaces 8-4
Cadcentre 8-57
Cadpipe example transfer 8-8
CADPIPE Example Transfer 8-8
CADPIPE Interface 8-4
Cadpipe log 8-19
CADPIPE LOG File Discussion 8-13
Cadpipe/CAESAR II data transfer 8-19
CADWorx Plant 3-94
CADWorx Plant database 2-10, 3-94
CADWorx Plant Link 8-4
CADWorx/PIPE directory 3-94
CADWorx/PIPE link 8-4
CAESAR II
4 Index
Fatal error processing 7-9
File guide 9-2
Initial capabilities (12/84) 10-2
Log file 8-21
Neutral file interface 8-57
Operational (job) data files 9-16
Version 1.1s features (2/86) 10-3
Version 2.0a features (10/86) 10-4
Version 2.1c features (6/87) 10-5
Version 2.2b features (9/88) 10-6
Version 3.0 features (4/90) 10-7
Version 3.15 features (9/91) 10-9
Version 3.16 features (12/91) 10-10
Version 3.19 features (3/93) 10-13
Version 3.20 features (10/93) 10-14
Version 3.21 changes & enhancements (7/94) 10-
15
Version 3.22 changes & enhancements (4/95) 10-
17
Version 3.23 changes (3/96) 10-18
Version 3.24 changes & enhancements (3/97) 10-
19
Version 4.00 changes and enhancements (1/98)
10-21
Version 4.10 changes and enhancements (1/99)
10-22
CAESAR II Fatal Error Processing 7-9
CAESAR II File Guide 9-2
CAESAR II Initial Capabilities (12/84) 10-2
CAESAR II interfaces 8-2
CAESAR II Local Coordinate Definitions 6-121
CAESAR II Log File 8-21
CAESAR II Neutral File Interface 8-57
CAESAR II Operational (Job) Data Files 9-16
CAESAR II Version 1.1S Features (2/86) 10-3
CAESAR II Version 2.0A Features (10/86) 10-4
CAESAR II Version 2.1C Features (6/87) 10-5
CAESAR II Version 2.2B Features (9/88) 10-6
CAESAR II Version 3.0 Features (4/90) 10-7
CAESAR II Version 3.1 Features (11/90) 10-8
CAESAR II Version 3.15 Features (9/91) 10-9
CAESAR II Version 3.16 Features (12/91) 10-10
CAESAR II Version 3.17 Features (3/92) 10-11
CAESAR II Version 3.18 Features (9/92) 10-12
CAESAR II Version 3.19 Features (3/93) 10-13
CAESAR II Version 3.20 Features (10/93) 10-14
CAESAR II Version 3.21 Changes and Enhancements
(7/94) 10-15
CAESAR II Version 3.22 Changes & Enhancements
(4/95) 10-17
CAESAR II Version 3.23 Changes (3/96) 10-18
CAESAR II Version 3.24 Changes & Enhancements
(3/97) 10-19
CAESAR II Version 4.00 Changes and Enhancements
(1/98) 10-21
CAESAR II Version 4.10 Changes and Enhancements
(1/99) 10-22
CAESAR II Version 4.20 Changes and Enhancements
(2/00) 10-23
CAESAR II Version 4.30 Changes and Enhancements
(3/01) 10-24
CAESAR II Version 4.30 Changes and Enhancements
(4/02) 10-24
CAESAR II Version 4.40 Changes and Enhancements
(5/02) 10-25
CAESAR II Version 4.50 Changes and Enhancements
(11/03) 10-26
CAESAR II Version 5.00 Changes and Enhancements
(11/05) 10-27
CAESAR II Version 5.10 Changes and Enhancements (
9/07) 10-28
Caesar.cfg 2-1
Calculate actual cold loads 3-115
Calculate Actual Cold Loads 3-115
Calculation of Fatigue Stresses 6-58
Can available space 3-47
CANADIAN Z662 6-94
CFE Sismo Example Problem 3-68
CFE Sismo Static Seismic Wizard 3-67
Change password 2-30
Change Password 2-30
Checking the CADPIPE/CAESAR II Data Transfer 8-
19
Checking the ComputerVision/CAESAR II Data
Transfer 8-21
Checking the PRO-ISO/CAESAR II Data Transfer 8-
55
Chopped strand mat 2-12, 3-14
Circumferential
(hoop) direction 3-75
Weld 3-25
Weld joint efficiency 3-73
Class 1
Flexibility calculations 2-25
Intersection flexibilities 6-12
Class 1 Branch Flexibilities 2-25, 6-12
Class 1 Branch Flexibility 2-25
Class 1 branch flexibilityClass 1 branch flexibility 2-
25, 6-12
Closely spaced mode criteria 5-54
Closely Spaced Mode Criteria/Time History Time Step
(ms) 5-54
CNode 3-40, 3-44, 3-133, 5-38
Coade technical support 1-4
COADE Technical Support 1-4
Code
Compliance 3-71, 6-16
Code Compliance Considerations 6-81
Code Options (B31.1 & B31.8) 3-28
Code-calculated 3-29
Code-calculated stress 3-29
Code-calculated values 3-29
Codes 3-71
Code-Specific Notes 6-84
Index 5
CODETI 6-103
Coefficient of Friction (Mu) 2-4, 3-43
Cold
Load design 3-45
Modulus 3-84
Spring 3-8, 3-10, 6-5
Spring element 6-5
Sustained 6-17
Cold load 3-51
Cold Spring 6-5
Columns 4-38
Fix 4-38
Free 4-38
COLUMNS 4-2, 4-38
Combining independent piping systems 3-128
Combining Independent Piping Systems 3-128
Combining static and dynamic results 5-26
Combining Static and Dynamic Results 5-26
Commands 1-1
Component Amplification Factor ap (ASCE) 3-66
Component Amplification Factor Rp (NBC) 3-70
Component Color 2-17
Component Elevation Ratio [hx/hn] (NBC) 3-70
Component Elevation Ratio z/h (ASCE) 3-66
Component Factor Cp (NBC) 3-70
Component Force Amplification Factor Ar (NBC) 3-
70
Compressed formatting 9-2
Computation control 2-3
Computational Control 2-3
Computational interfaces 8-76
Computational Interfaces 8-76
Computed Mass Flow Rate 5-76
Computed mass flowrate 5-73, 5-76
Computed Mass Flowrate (Vent Gas) 5-73
Computervision interface 8-20
ComputerVision Interface 8-20
ComputerVision Interface Prompts 8-20
Computervision neutral file 8-20, 8-21
ComputerVision Neutral File 8-20
Computervision/CAESAR II data transfer 8-21, 8-24
Conclusion 6-79
Condense Connected Rigids 8-56
Condense Elbows 8-56
Condense Tees 8-56
Configuration 1-1
Program 3-7
Spreadsheets 2-1
Configuration and Environment 1-2, 2-1, 6-81
Configure
/Setup 3-106
Button 2-1
Connect geometry through CNodes 2-15
Connect Geometry Through CNodes 2-15, 3-40
Connecting nodes 2-15, 3-40
Conservative cutoff 5-53
Constant effort hanger 6-11
Constant effort support 6-11
Constant Effort Support 6-11
Constant force value 6-15
Control
Parameters 1-1
Control information 8-58
Control Information 8-58
Controlling the Data Export 8-84
Controlling the dynamic solution 5-3
Controlling the Dynamic Solution 1-2, 5-1
Convergence error 2-6
Convert input to new units 7-13
Convert Input to New Units 7-13
Convolutions 3-110
Coordinate prompts 3-119
Corroded
Cases 2-24
Corrosion 2-24, 3-8
Covers 3-113
Cpu time used 7-1
Crane database 2-10, 3-94
Create a new units file 7-11
Create a New Units File 7-11
Create Loop on Element 3-135
Create table 5-17
Create Table 5-17
Creating the .FAT Files 6-57
Creep rupture design stress value 3-82
Creep rupture stress 3-73
Critical damping 5-55
Cross Section (Section ID) 4-6
Cross section area 4-16
Crotch Radius 3-100
CROTCH R 3-26
Crotch radius 3-25
Current data 6-32
Current Data 6-32
Current profile 6-26
Curve boundary 3-53
Curved pipe 3-25
Cut long 6-5
Cut short 3-8, 6-5
Cutoff
See non-conservative, conservative, and optimal
5-53
Cyclic frequency 5-44
Cyclic reduction factor fields 3-84
D
Damped harmonics 5-41
Damping 5-41
Damping (Time History or DSRSS) (Ratio of Critical)
5-55
Damping (time history or dsrss) (ratio of
critical)Damping 5-55
6 Index
Damping matrix 5-41
Damping ratio 5-48, 5-60
Data
Files 9-2, 9-16
Set 9-2
Data Export to ODBC Compliant Databases 8-81
Data Export Wizard 8-84
Data matrix interface 8-43, 8-74
Data Matrix Interface 8-74
Data Modification and Details 8-24
Database definitions 2-8
Database Definitions 2-8
database management 8-81
Decomposition singularity tolerance 2-4, 5-65
Decomposition Singularity Tolerance 2-4, 5-65
Default code 2-25
Default Operator 2-18
Default Piping Code 2-25
Default Projection 2-18
Default Render Mode 2-18
Default restraint stiffness 2-4
Default rotational restraint stiffness 2-4
Default Rotational Restraint Stiffness 2-4
Default spring hanger table 2-8
Default Spring Hanger Table 2-8
Default translational restraint stiffness 2-4
Default Translational Restraint Stiffness 2-4
Default View 2-18
Defaulting to Z-Axis Vertical 3-123
Defaulting to Z-AxisVertical 3-123
Defining a Model 6-118
Defining Global Restraints - FIX 4-2, 4-40
Delete 3-131, 4-10
Delta x 3-3
Delta y 3-3
Delta z 3-3
Dens 4-14
DENS 4-14
Densities 3-11
Density 3-11, 7-16
Depth-decay function 6-29
Description of Alternate Simplified ASME Sect. VIII
Div. 2 Nozzle Analysis 6-38
Design (Button) 3-136
Design Factor (Unitless) 3-82
Design strain 2-12
Design stress 3-73
Det Norske Veritas (DNV) 6-108
Diagnostics-error review 7-9
Diagonal damping matrix 5-48
Diagonal stiffness matrix 5-48
Diameter 3-5
Diameter 2 3-22
Diameter field 3-5
Diffraction effects 6-29
Direction 5-9, 5-11, 5-19, 5-31, 5-35, 5-37
Directional combination method 5-62
Directional Combination Method (SRSS/ABS) 5-62
DIRECTIVE DATA 5-26
Directives 5-21
Directory structure 9-2
Disable 2-20
Disable Undo/Redo Ability 2-20
Displaced Shape 2-19
Displacement 3-60, 5-11
Loads 6-5
Range 6-16
ReportsDisplacement
Reports 2-21
Vector 5-41, 5-48
Displacement Reports Sorted by Nodes 2-21
Displacements 3-60
Distance to opposite-side stiffener or head 3-55
Distance to Opposite-Side Stiffener or Head 3-55, 3-
59
Distance to stiffener or head 3-55
Distance to Stiffener or Head 3-55, 3-59
DLF curves 5-69
Do/r3 3-33
Does the vent pipe have an umbrella fitting (y/n) 5-71
Does the Vent Pipe Have an Umbrella Fitting (Y/N)
5-71
Double Angles - Long Legs Back-to-Back 4-54
Double Angles - Short Legs Back-to-Back 4-55
Double Sum Method (DSRSS) 5-60
Drag coefficient 6-34
Drag Coefficient, Cd 3-64
Draw Cube 3-136
Driving frequency 5-67
DSN Setup 8-81
Duplicate 3-131
Duplicate dialog box 3-131
DX 3-3
DX, DY, DZ 4-21, 4-28
DXF AutoCAD Interface 8-4
DY 3-3
Dynamic
Analyses 5-49
Analysis input 5-2
Control parameters 1-1
Displacement criteria 5-67
Earthquake 6-20
Earthquake loading 3-121
Equation of motion 5-41
Example input textDynamic
Example input text 2-21
Input 1-1
Input processor 5-39
Load 5-3
Load factor 5-41, 5-44, 5-51, 8-76, 8-80
Load factor spectrum 5-44
Loads 5-41
Problem 5-41
Dynamic Analysis Input 5-2
Index 7
Dynamic Analysis Overview 5-3
Dynamic control parameters 5-39
Dynamic Control Parameters 5-39
Dynamic Example Input Text 2-21
Dynamics 9-11
DZ 3-3
E
Earthquake
Effects 5-3
Load 5-44
Load magnitudes 6-20
Loads 3-121
Spectrum 5-56
Static load cases 6-20
EDIM 4-2, 4-27
Eff 3-81
Eff, cf, z 7-15
Eff, Cf, z 7-15
Effective ID 3-21
Efill 4-23
EFILL 4-2, 4-23
Egen 4-25
EGEN 4-2, 4-25
Eh / Ea 3-90
Eigensolution 5-44
Eigensolver algorithm 5-44
Eigenvalue 5-44
Eigenvalues 5-64
Elastic
Modulus 3-84
ModulusElastic
Modulus 7-17
Elastic analyses of nozzles 6-37
Elastic Modulus 3-106, 7-17
ELEM 4-2, 4-22
ElemBuilding elements
Elem, efill, egen, edim 4-22
Element
Duplication 3-131
List 3-130
Offsets 3-5
RotationDelete 3-131
Element Cosines 3-4
Element Direction Cosines 3-4
Element Length 3-4
Element Offsets 3-5
Element/Node/Stress/Restraint Load Component 3-
135
Elevation 6-24
Elevation table entry 6-22
EN-13480 6-109
EN-13480 - Use In-Plane/Out-Plane SIF 2-25
Enable Advanced Element Sort 8-23
Enable Autosave 2-21
Enable Data Export to ODBC-Compliant Databases
2-8
End connection information 4-32
End Connection Information 4-32
Ending frequency 5-7
Ending Frequency 5-7
Endurance limit 5-41
Entity information 8-14
Equation
for pipe under complete axial restraint 3-84
for stress 3-84
Equipment vibration 5-3
Equivalent wind pressure 6-22
Error code definitions 8-15
Error Code Definitions 8-13
Estimated Number of Significant Figures in
Eigenvalues 5-64
Evaluating vessel stresses 6-36
Evaluating Vessel Stresses 6-36
Example 4-21, 4-24, 4-26, 4-31, 4-35, 4-37, 4-39, 4-
40, 4-42, 4-44, 4-47, 5-15, 8-77, 8-78
Example 1 8-77
Example 2 8-78
Example Problem
Multiple Load - Case Spring - Hanger Design 3-50
Example problem of a multiple load-case spring-hanger
design 3-50
Example transfer 8-25
Example Transfer 8-25
Examples 4-28, 4-31, 4-40, 4-42, 4-44, 4-47, 9-15
Excel 8-81
Exclude f2 from UKOOA Bending Stress 2-12
Exe files - required 9-2
Existing file to start from 7-12
Existing File to Start From 7-12
Exit pipe end flow conditions 5-76
Exp. Coeff. 7-17
Exp. coeff. Expansion
Coefficient 7-17
Expansion
Case allowable stress 3-84
Coefficient 3-84
Stress 3-84, 6-16
Stress allowable 3-82
Stress range 6-16, 6-17
Expansion joint design notes 3-110
Expansion Joint Design Notes 3-110
Expansion joint end-types 3-111
Expansion Joint Modeler 3-106
Expansion Joint Modeler - Expansion Joint Database
3-108
Expansion Joint Modeler - From / To Nodes 3-108
Expansion Joint Modeler - Hinge/Pin Axis 3-108
Expansion Joint Modeler - Modeler Results 3-109
Expansion Joint Modeler - Overall Length 3-108
Expansion Joint Modeler - Tie Bar Plane 3-108
8 Index
Expansion Joint Modeler Notes 3-109
Expansion Joint Styles 3-111
Expansion joints 2-9, 3-20, 3-119, 6-7
Database 2-9
Model 3-106, 3-109
Modeler 3-106, 3-109
Styles 3-111
Expansion Joints 2-9, 2-17, 3-20, 3-109, 6-7
Exponential format 3-3
Extended
Operating conditions 3-8, 3-9
Range 3-45
External interface 8-2
External Interfaces 9-14
Extracted 2-6
F
Fac 3-84, 7-16
FAC 7-16
Factor 5-19, 5-26
Fatigue
Curve data 3-87
Cycle 3-77
Evaluations 3-87
Factor 3-77
Fatigue Analysis of Piping Systems 6-45
Fatigue Analysis Using CAESAR II 6-44
Fatigue Basics 6-44
Fatigue Capabilities in Dynamic Analysis 6-55
Fatigue Class 3-38
FDBR 6-104
Fiberglass reinforced plastic 3-10, 3-14, 3-119
Fiberglass Reinforced Plastic (FRP) 3-10
File Name 8-22, 8-56
File Sets 1-2, 9-1
Files
-Clean up 9-2
Files-accounting 7-6
Fillet 3-25
FILLET 3-26
Fillet weld 3-87
Filter Out Elements Whose Diameter is Less Than 8-
23
Final CAESAR II data 8-18
Find Distance 3-97
Find Element 3-98
Finite length expansion joints 3-20
Finite Length Expansion Joints 3-20
First Mode Period (CFE) 3-68
Fitting
Flexibility factor 2-13
Outside radius 3-25
Thickness 3-15
Fitting Outside Radius 3-100
Fitting Thickness 3-15, 3-104
Flange Class & Material Grade 3-18
Flange database 3-94
Flange leakage and stress calculations 10-9
Flange Leakage and Stress Calculations 10-9
Flanged ends 3-94
Flanges 3-17
Flexibility
Analysis 3-84
Factor 2-13, 3-10, 3-14
Matrix 6-16
Orientation 3-54
Fluid
Bulk modulus Fluid
Bulk modulus 5-75
Density 3-11, 5-75
Hammer 5-5
Loads 6-26
Fluid Bulk Modulus 5-75
Fluid Density 3-11, 5-75
Fn 3-77
Force 5-9, 5-18, 5-31, 5-48
Orthogonalization after convergence 5-65
Sets 5-48
Spectrum 5-5
Spectrum analysis Force
Spectrum analysis 5-44
Spectrum name 5-17
Force Consistent Bend Materials 8-23
Force Orthogonalization After Convergence (Y/N) 5-
66
Force orthogonalization after convergence (y/n) Force
Orthogonalization after convergence 5-66
Force response spectrum definitions 5-17
Force Response Spectrum Definitions 5-17
Force set # 5-20, 5-31
Force Set # 5-20, 5-31
Force Spectrum Name 5-17
Forces 3-61, 3-110
Forces and moments 3-61
Forces and Moments 3-61
Forces at elbows 5-5
Free
Anchor/restraint at node 3-50
Code 3-51
End connections 4-32
Free Anchor/Restraint at Node 3-50
Free Code 3-51
Free End Connections - FREE 4-2, 4-32
French petrochemical code 6-17
Frequency
Array spaces Frequency
Array spaces 5-66
Cutoff 5-51
Cutoff Frequency
Cutoff 5-53
Frequency Array Spaces 5-66
Frequency Cutoff (HZ) 5-53
Frequently Asked Questions 6-130
Index 9
Friction
Angle variationFriction
Angle variation 2-4
Coefficient 3-43
Normal force variation Friction
Normal force variation 2-4
Restraint stiffness 2-4
Slide multiplier Friction
Slide multiplier 2-4
Stiffness factor 5-50
Stiffness Friction
Stiffness 2-4
Friction Angle Variation 2-4
Friction Normal Force Variation 2-4
Friction Slide Multiplier 2-4
Friction Stiffness 2-4
From 3-2
From/To/Both 3-17
FRP
Alpha FRP
Alpha 2-12
Coefficient of thermal expansion 3-121
Data 9-2
Laminate type 2-12
Modulus of elasticityFRP
Modulus of elasticity 2-11
Pipe density FRP
Pipe density 2-12
Pipe properties Fiberglass reinforced plastic 2-11
Property data file FRP
Property data file 2-12
Ratio of shear modulus/emod axial 3-122
FRP Alpha (xe-06) 2-12
FRP Analysis Using CAESAR II 6-73
FRP Coefficient of Thermal Expansion (x 1,000,000 )
3-121
FRP Density 2-12
FRP flexibilities 2-13
FRP Laminate Type 2-12, 3-122
FRP Pipe Properties 2-11
FRP Property Data File 2-12
FRP Ratio of Shear Modulus/Emod Axial 3-122
FRP sif 2-13
Ftg ro 3-25
FTG RO 3-26
G
G 4-14
Gap 3-42
Gasket Diameter, G / Bolt Circle 3-18
Gas-specific heats 5-71
General notes 8-13
General Notes 8-13
General Notes for All Codes 6-81
General properties 4-10
General Properties 4-10
Generation of the CAESAR II configuration file 2-1
Generation of the CAESAR II Configuration File 2-2
Generic database 3-94
Generic neutral files 8-57
Generic Neutral Files 8-57
Geninc 4-26
GENINC 4-26
Genincto 4-26
GENINCTO 4-26
Genlast 4-26
GENLAST 4-26
Geometry directives 2-14
Geometry Directives 2-14
German 1991 database 4-62
German 1991 Database 4-62
German 1991 Database - 1 4-62
German 1991 Database - 2 4-63
Gimbal 3-112
Global
Editing 3-131
Level 3-49
Load vector 6-15
Stiffness matrix 6-10
X direction 3-3
Y direction 3-3
Z direction 3-3
Global Coordinates 3-98, 3-120
Global restraints - fix 4-40
GPTC/Z380 6-109
Gram-schmidt orthogonalizations 5-65
Graphic Settings 2-16
Gravitational acceleration constant 6-20
Gravitational loading 3-121
Gravity loads - gloads 4-45
Gravity Loads - GLOADS 4-2, 4-45
Grinnell springs 3-45
Group modal combination method 5-54
Grouping method 5-59
Grouping Method 5-59
Guide 3-41
H
Hand Lay 3-90
Hanger
Algorithm 6-10
Data 3-114
Default restraint stiffness Hanger
Default restraint stiffness 2-5
10 Index
Design 6-9
Design algorithm 6-9
Design control dialog 6-10
Design control spreadsheet 3-49, 3-114
Hot loads 6-9
Run control spreadsheet 3-45
Sizing algorithmFiles
CompatibilityFiles
Compatibility 6-9
Table 3-45
Travel 6-9
Type restraint 3-42
Hanger available space 3-47
Hanger Data 3-45, 3-49, 3-114, 3-117
Hanger Default Restraint Stiffness 2-5
Hanger Sizing Algorithm 6-9
Hanger Table 3-45, 3-116
Hanger/Can Available Space 3-47
Hangers 2-17, 3-44
Harmonic 5-3
Analysis 5-41, 5-67, 6-22
Analysis Harmonic
Analysis 5-41
Displacements 5-11
Equation 5-41
Forces and displacements 5-9
Load 5-67
Load vector 5-41
Method 5-3
Harmonic Analysis 5-7, 5-41
Harmonic Displacements 5-11
Harmonic Displacements at Compressor Flange 5-12
Harmonic Forces and Displacements 5-9
HarmonicHarmonic
Profile 5-3
Header Pipe Outside Diameter 3-103
Header Pipe Wall Thickness 3-103
Header stress intensification 3-29
Help screen 3-3
Help screens and units 3-2
Help Screens and Units 3-2
Hinged 3-112
hl(1
1) Long Term Hoop Stress at 1
1 Stress Ratio 3-88
hl(2
1) Long Term Hoop Stress at 2
1 Stress Ratio 3-89
Hoop
Direction 3-73
Elastic modulus 2-11
Modulus 3-10
Stress 3-84
Stress value 2-25
Horizontal thermal bowing tolerance 2-15
Horizontal Thermal Bowing Tolerance 2-15
Horizontal threshold value 2-15
Hot
Hanger loads 3-50
Load 3-45, 6-9
Load design 3-45
Modulus 3-84
Sustained 6-17
How to Use the CAESAR II / LIQT Interface 8-76
How to Use the CAESAR II / PIPENET Interface 8-
80
HPGSL 6-110
Hydrodynamic (Wave and Current) Loading 6-25
Hydrodynamic loads 6-26
I
ID manifold piping 5-75
ID Manifold Piping 5-75
ID of relief valve orifice 5-70
ID of Relief Valve Orifice 5-70
ID of relief valve piping 5-70
ID of Relief Valve Piping 5-70
ID of vent stack piping 5-70
ID of Vent Stack Piping 5-70
ID relief exit piping 5-75
ID Relief Exit Piping 5-75
ID relief orifice or rupture disk opening 5-75
ID Relief Orifice or Rupture Disk Opening 5-75
ID supply header 5-75
ID Supply Header 5-75
Idealized
Allowable stress envelope 3-77
Identical results 2-1
IEEE 344-1975 5-58
IGE/TD/12 6-108
IGE/TD/12 Code 3-7, 3-16, 3-87
IGE\TD\12 Requirements 3-31
Ignore B31.3 Wc Factor 2-26
Ignore Spring Hanger Stiffness 2-5
Implement B31.3 Appendix P 2-26
Implement B31.3 Code Case 178 2-26
Implementation of Macro-Level Analysis for Piping
Systems 6-67
Import / Export Displacements 3-134
Importance factor 6-20, 6-22
Importance Factor IE (NBC) 3-69
Importance Factor Ip (ASCE) 3-65
Impulse 5-5
Impulse profile 5-5
INC 4-23, 4-26, 4-27, 4-30, 4-33, 4-44, 4-46
Include
Include Missing mass components (y/n)
Missing mass components 5-62
Piping input files 3-128
Pseudostatic (anchor movement)
componentsInclude
Pseudostatic (anchor movement) components 5-61
Index 11
Include Additional Bend Nodes 8-23
Include Insulation in Hydrotest 2-5
Include Missing Mass Components (Y/N) 5-62
Include Pseudostatic (Anchor Movement) Components
(Y/N) 5-61, 5-62, 5-63
Include Spring Stiffness in Hanger OPE Travel Cases
2-5
Included force 5-51
Included mass 5-51
Including Structural Models 3-129
Including the Spring Hanger Stiffness in the Design
Algorithm 6-11
Inclusion of Missing Mass Correction 6-40
Incmatid 4-26
Incmatid 4-24
INCMATID 4-24, 4-26, 4-28
Incore numerical check 2-5
Incore Numerical Check 2-5
Increase Factor (CFE) 3-68
Increment 4-23, 4-26, 5-7, 5-10, 5-12, 5-20, 5-36
Incsecid 4-24, 4-26
INCSECID 4-24, 4-26
Incto 4-24
Incto 4-24
INCTO 4-24, 4-26, 4-28, 4-30, 4-33, 4-44, 4-47
Independent shock 5-58
Independent support motion 5-44, 5-61
Independent support motion applications 5-44
Independent support motion load cases 5-62
Inertia coefficient 6-34
In-line Flange Evaluation 6-3
In-plane stress intensification 3-29
Input
Data cells 3-2, 3-71
Dynamic 9-16
Echo 3-133
Fields 1-1
Soil 9-16
Specifying Hydrodynamic Parameters in CAESAR
II 6-32
Static 9-16
Structural 9-16
Input Excitation Frequencies 5-7
Input items optionally effecting sif calculations 3-25
Input Items Optionally Effecting SIF Calculations 3-
25
Input Items Optionally Effecting SIF Calculations For
ISO 14692 3-28
Input listing 3-133
INSECID 4-28
Insert 4-10
Insert Element 3-98
Insert weldolets 3-25
Installation directory 2-1
Installed load 6-10
Installed load case 6-10
Installed Load Case 6-10
Installed weight 6-10
Insul thk 3-8
Insul Thk 3-8
Insulation 3-8
Insulation Density 3-11
Insulation Units 8-24
Interfaces 1-1, 1-2, 8-1
Intergraph
Data 8-37
Interface 8-24
Intergraph Data After Bend Modifications 8-43
Intergraph data after element sort 8-35
Intergraph Data After Element Sort 8-35
Intergraph data after tee/cross modifications 8-36
Intergraph Data After TEE/Cross Modifications 8-36
Intergraph data after valve modifications 8-37
Intergraph Data After Valve Modifications 8-37
Intergraph interface 8-22
Intergraph Interface 8-22
Intermodal correlation coefficient 5-60
Interpolation parameters 2-7
Intersection model 3-23
Intersections 3-25
Introduction 1-1
Iso 8-4
ISO-14692 6-109
Ixx 4-16
Iyy 4-16
J
Jacobi sweep tolerance 5-64
Jacobi Sweep Tolerance 5-64
Jacobus 8-57
JIS nominal pipe od 3-5
JIS pipe schedule 3-7
Joint endtypes 3-109
JPI 6-110
K
k - Thermal Factor 3-92
K2 3-41
Kaux 3-128
Kellogg Equivalent Pressure Method 6-3
Keulegan-carpenter number 6-29
K-Factor 3-16
Kinematic viscosity 6-34
Korean 1990 database 4-66
Korean 1990 Database 4-67
Ksd. (Factor) (Unitless) 3-86
L
L1/Lb 3-34
Laminate
Type 2-12, 3-14
Last 4-24, 4-26, 4-28, 4-30, 4-33, 4-47
12 Index
LAST 4-21, 4-24, 4-26, 4-30, 4-33, 4-44, 4-47
Lateral force 6-20
Legend Text 2-17
Length of manifold piping 5-75
Length of Manifold Piping 5-75
Length of relief exit piping 5-75
Length of Relief Exit Piping 5-75
Length of the vent stack 5-71
Length of the Vent Stack 5-71
Liberal Expansion Stress Allowable 2-26
Liberal Stress Allowable 3-120
Lift coefficient 6-34
Lift Coefficient, Cl 3-64
Lift force 6-26
LIM 3-41
Line
Pressure Line
Pressure 5-70
Temperature Line
Temperature 5-70
Line Pressure 5-70
Line Temperature 5-70
Liners 3-113
LIQT interface 8-76
LIQT Interface 8-76
LIQT nodes 8-76
Liquid vent system 5-74
List 4-48
LIST 4-2, 4-48
List option 3-130
List utility 3-128
List/ Edit Facility 3-130
List/edit facility 3-130
Listing 9-16
Load
Duration 5-60
Forcing frequency 5-55
Profiles 5-48
Range 3-45
Load case 5-26
Load Case 5-26
Load Case (for Design) 3-134
Load Case Template 2-9
Load Cycles 5-8
Load Duration (Time History or DSRSS Method)
(Sec.) 5-55
Load duration (time history or dsrss method)Load
Duration 5-55
Load vector
Applied 5-41
Loads 4-42
Local Coordinates 6-112
Local flexibilities 6-12
Local stresses 6-36
Log file 8-22
Longitudinal
Stress 2-28
Longitudinal weld joint efficiency 3-73
Loop closure tolerance 2-15, 3-119
Loop Closure Tolerance 2-15
Loop Optimization Wizard 3-134, 3-137
Loop Type 3-136
Lumped Masses 5-35
M
Macro-Level Analysis 6-66
Major Direction 3-136
Major Direction Available Space 3-136
Make units file 7-10
Make Units File 7-10
Manifold pipe end flow conditions 5-76
Manifold piping 5-75
Marine growth 6-29
Marine Growth 3-64
Marine Growth Density 3-64
Marker Settings 2-18
Mass 5-35
Flowrate 5-73, 5-76
Matrix 5-41
Matching Pipe Outside Diameter 3-105
Material
- Add 7-14
- Delete 7-14
- Edit 7-15
Coefficient of thermal expansion 4-14
Database 9-2
Database Material
Database 7-14
Density 4-14
Files 2-12
ID number 4-13
Identification Material
Identification 4-13
Name 3-10
Properties 3-10
Material - Add 7-14
Material - Delete 7-14
Material - Edit 7-15
Material Database 7-14
Material Fatigue Curves 3-87
Material Identification - MATID 4-2, 4-13
Material Name 3-10
Material Properties 3-10, 4-5
Materials 3-10, 3-113
Matid 4-13
Matid 4-24
Matid 4-26
MATID 4-13, 4-24, 4-26, 4-28
Max. no. of Eigenvalues calculated 5-51
Max. No. of Eigenvalues Calculated (0-Not used) 5-
51
Max. Stress 3-135
Index 13
Maximum
Shear theory 2-28
Maximum Allowable Bend Angle 2-15
Maximum allowed bend angle 2-15
Maximum allowed travel limit 3-48
Maximum Allowed Travel Limit 3-48, 3-116
Maximum Anchor Node 8-23
Maximum Mapped Response Acceleration Ss (ASCE)
3-65
Maximum Pressure 3-106
Maximum table frequency 5-17
Maximum Table Frequency 5-17
Mechanical resonances 5-67
Member weight load 4-44
Memory allocated 2-21
Memory Allocated (Mb): 2-21
Menu
Items 1-1
Miche limit 6-26
Micro-Level Analysis 6-60
Mill tol % 3-7
-Mill Tol % 3-7
Mill tolerance 3-7
Mini-Level Analysis 6-64
Minimum
Allowed bend angle 2-15
Angle to adjacent bend 2-15
Temperature curve 7-16
Wall mill toleranceMinimum
Wall mill tolerance 2-5
Yield strength 3-82
Yield stress 3-82
Minimum Allowable Bend Angle 2-15
Minimum Anchor Node 8-23
Minimum Angle to Adjacent Bend 2-15
Minimum Temperature Curve (A-D) 7-16
Minimum Wall Mill Tolerance (%) 2-5
Minor Direction 3-136
Minor Direction Available Space 3-136
Miscellaneous 2-20, 10-9
Data group 8-68
Miscellaneous Data Group #1 8-68
Miscellaneous Options 2-17, 2-20
Miscellaneous Processors 1-2, 7-1
Missing
Mass 5-51
Mass combination method Missing
Mass combination method 5-62
Mass correction 5-62
Mass ZPAMissing
Mass ZPA 2-6
Missing Mass Combination Method (SRSS/ABS) 5-
62
Missing Mass ZPA 2-6
Miter points 3-14
Miter Points 3-14, 3-105
Miters 3-14
Modal
Combination method Modal
Combination method 5-59
Combinations 5-58
Components 5-58
Extraction 5-41
ExtractionModal
Extraction 5-44
Modal Combination Method
(GROUP/10%/DSRSS/ABS/SRSS) 5-59
Mode shape 5-44, 5-48, 5-67
Model - expansion joint menu 3-106
Model Definition Method 4-8
Model Rotation 8-24, 8-56
Model Tees as 3 Elements 8-24
Modeling friction effects 6-15
Modeling Friction Effects 6-15
Modeling techniques 1-1
Modes of vibration 5-44
Modified theories 6-29
Modifying mass lumping 5-35
Modulus of elasticity 3-10
Modulus ratio 3-84
Moments 3-61, 3-110
Morrison's equation 6-26
Movement capability 3-110
Movement Capability 3-110
Mu 3-43
Multi-degree-of-freedom system 5-55
Multiple load case design 3-49, 3-118
Multiple Load Case Design 3-49
Multiple Load Case Design Options 3-118
N
n1 4-20, 4-23, 4-25, 4-27, 4-30, 4-32, 4-43, 4-46
N1 4-20, 4-23, 4-25, 4-30, 4-32, 4-43
Name 3-3, 4-15, 5-13, 7-15
Name of the converted file 7-13
Name of the Converted File 7-13
Name of the input file to convert 7-13
Name of the Input File to Convert 7-13
Name of the units file to use 7-13
Name of the Units File to Use 7-13
Natural frequency 5-44
NAVY 505 6-96
NBC Example 3-70
NBC Static Seismic Wizard 3-69
Neutral file 8-74
Neutral file interface 8-57
Neutral file transfer 8-2
New File 4-3
New Job Ambient Temperature 2-6, 3-121
New Job Bourdon Pressure 2-6
14 Index
New Job Liberal Expansion Stress Allowable 2-26, 3-
120
New Password 2-30
New units file name 7-12
New Units File Name 7-12
Nfill 4-19
NFILL 4-2, 4-19
Ngen 4-20
NGEN 4-2, 4-20
No rft/wlt in reduced fitting sifs 2-26
No RFT/WLT in Reduced Fitting SIFs 2-26
No. hangers at location 3-48
No. Hangers at Location 3-48
No. of Hanger - Design Operating Load Cases 3-114
No. of hanger-design operating load cases 3-114
No. of Iterations Per Shift (0 - Pgm computed) 5-65,
5-66
No. of iterations per shift (0-pgm computed) 5-65
No. to Converge Before Shift Allowed (0 - Not Used)
5-65
No. to converge before shift allowed (0-not used) 5-
65
Nodal coordinate data 8-74
Nodal Coordinate Data 8-74
Nodal displacements 6-15
Node 2-15, 3-14, 3-40, 3-44, 4-18, 5-31, 5-37
Number 3-2, 3-14, 3-29, 3-40
NODE 4-2, 4-18
Node Increment 3-98
Node number 3-2
Node Number 3-25, 3-32
Node Number Increment 8-23, 8-56
Node Text 2-17
NODEINC 4-21
Nodes 3-133
Nodes in space 4-18
Nominal pipe OD 3-5
Nominal pipe schedules 3-5
Non-conservative cutoff 5-53
Nonlinear
Code compliance Nonlinear
Code compliance 6-16
Piping code compliance 6-16
Restraint 6-16
Nonlinear Code Compliance 6-16
Nonlinear restraints 6-17
Norwegian (TBK 5-6) 6-103
Notes on Occasional Load Cases 6-18
Nozzle
Auxiliary data field 3-39, 3-53, 3-56
Flexibilities 3-39
Nozzle diameter 3-55
Nozzle Diameter 3-55, 3-56, 3-59
Nozzle flexibility - WRC 297 3-53
Nozzle Flexibility - WRC 297 3-53
Nozzle node number 3-54
Nozzle Node Number 3-54, 3-56, 3-58
Nozzle wall thickness 3-55, 3-57
Nozzle Wall Thickness 3-55, 3-57
Nozzles 2-17, 3-52
Nuclear Regulatory Guide 1.92 5-58
Number 7-15
Number formats 3-3
Number of points in the table 5-17
Number of Points in the Table 5-17
O
Occasional
Load factor 2-26
Load factor Occasional
Load factor 2-26
Occasional Load Factor 2-26
Ocean currents 6-28
Ocean Currents 6-28
Ocean Wave Particulars 6-25
ODBC 8-81, 8-84
ODBC Compliant Database Name 2-9
Off 3-64
Off-diagonal coefficients 2-4
Offsetting 6-5
On Element 3-135
On-diagonal coefficient 2-4
Operating
Analysis 6-16
Case 6-9
Case vertical displacement 6-9
Load field 3-49
Loads 3-45, 3-49
Pressure 3-88
Temperature 3-84
Thermal cases 3-49
Operating Case 6-9
Operating Load 3-49
Optimal cutoff 5-53
Optimal Frame Rate 2-18
Optimization Type 3-134
Ordinate 5-16
Ordinate Interpolation 5-14
Ordinate Type 5-14
Orient 4-30
ORIENT 4-2, 4-30
Orienting a Piping model to Z-axis Vertical 3-123
Orienting a Piping Model to Z-Axis Vertical 3-123
Orienting a Structural Model to Z-Axis Vertical 3-127
Orienting a Structural Model to Z-Axis Vertical. 3-
127
Orienting an Equipment Model to Z-Axis Vertical 3-
127
Orienting an Equipment Model to Z-Axis
VerticalOrienting an Equipment Model to Z-
Axis Vertical 3-127
Orifice flow conditions 5-76
Index 15
Orifice Flow Conditions/Exit Pipe End Flow
Conditions/Manifold Pipe End Flow
Conditions 5-76
Ortho 8-4
Orthogonal 3-43
Other Global Coordinate Systems 6-113
Other Notes on Hanger Sizing 6-11
Out-of-core eigensolver (y/n) 5-66
Output 9-16
Processor 5-48
Output Colors 2-19
Output from the liquid relief load synthesizer 5-76
Output From the Liquid Relief Load Synthesizer 5-76
Output Reports by Load Case 2-21
Output reports by load case output
Reports by load case 2-21
Output table of contents
Table of contents 2-21
Output Table of Contents 2-21
Overview 1-1, 1-2, 4-2
Overview of CAESAR II Interfaces 8-2
P
Pad Thickness 3-99
Pad thk 3-25
PAD THK 3-26
PCF Interface 8-55
PD 5500 Nozzles 3-58
PD 5500 radio button 3-58
PD/4t 2-28
PDMS 8-57
Peak pressure 3-88
Peq/NC-3658.3 Selection 3-17
Percent of iterations per shift before orthogonalization
5-66
Percent of Iterations Per Shift Before Orthogonalization
5-66
Period 5-44
Phase 5-10, 5-11
Phase angle 5-10, 5-11
Pipe
Density 3-10, 3-11
Element exposed area 6-22
Element spreadsheet 3-5, 3-61, 3-62, 3-63, 3-64,
3-71, 6-7
Outside diameter 3-55
Schedules 3-7
Section data 3-5
Size 2-9
Spreadsheet 3-106, 3-113
Pipe Density 3-11
Pipe Section Data 3-5
Pipe Stress Analysis Coordinate Systems 6-115
Pipe Stress Analysis of FRP Piping 6-60
Pipenet interface 8-79, 8-80
PIPENET Interface 8-79
Pipes 2-17
Piping
Codes 3-71
Element data 6-34
Materials 3-10
Screen reference 1-1
Size specification Piping
Size specification 2-9
Spreadsheet 3-71
Spreadsheet data 3-2
System model 5-41
Piping Element Data 6-34
Piping Materials 3-10
Piping Screen Reference 1-2, 3-1
Piping Size Specification (ANSI/JIS/DIN/BS) 2-9
Piping Spreadsheet Data 3-2
Plant space 8-57
Plastic pipe 3-10
Plate 3-111
Plot screen 1-1
Point loads - load 4-42
Point Loads - LOAD 4-2, 4-42
Pois 4-14
POIS 4-14
Poisson's ratio 2-11, 3-10, 3-84, 4-14, 7-16
Poisson's Ratio 7-16
Polar moment of inertia 4-16, 4-49
Practical Applications 6-73
Predefined
El centro 5-44
Hanger data 3-51
Nuclear Regulatory Guide 1.60 5-44
Uniform building code 5-44
Predefined Hanger Data 3-51
Pressure 3-9
Peaks 5-67
Pulses 5-67
Rating 3-111
Stiffening 2-6
Stress multiplier 3-25
Thrust 6-7
Pressure / Temperature Grid 3-19
Pressure Rating 3-111
Pressure stiffening 2-6
Pressure Variation in EXP Case 2-27
Pressures 3-9
Pricing factors 7-1
Primary membrane stress 6-36
Primary stress index 3-25
Print alphas and pipe properties 3-119
Print Alphas and Pipe Properties 3-119
Print forces on rigids and expansion joints 3-119
Print Forces on Rigids and Expansion Joints 3-119
Printer/listing files 9-2
Printing an input listing 3-133
Printing an Input Listing 3-133
16 Index
Procedure to Perform Elastic Analyses of Nozzles 6-
37
Program support / user assistance 1-3
Program Support / User Assistance 1-3
PRO-ISO example transfer 8-53
PRO-ISO Example Transfer 8-53
PRO-ISO interface 8-43
PRO-ISO Interface 8-49
PRO-ISO/CAESAR II data transfer 8-55
Prompted Autosave 2-21
Prompted Auto-Save 2-21
Proof stress 3-73, 3-82
Propagate Properties 3-8
Pseudostatic
Combination method Pseudostatic
Combination method 5-62
Displacement 5-44
Hydrodynamic loading 6-26
Responses 5-62
Pseudostatic (Anchor Movement) Comb. Method
(SRSS/ABS) 5-62
Pseudo-Static Hydrodynamic Loading 6-26
Publication dates 3-71
Pulsation 5-3
Pulsation loads 5-67
Pulsation Loads 5-67
Pulse table generator 5-17
Pulse table/dlf spectrum generator 5-44
Pvar 3-88
Q
Qs - Qualified Stress for Joints, Bends and Tees 3-89
R
r - Bi-Axial Stress Ratio for Bends, Tees and Joints 3-
90
R1 3-23
r1/Tc/Lh 3-34
R2 3-23
r2/rc 3-34
Radius 3-13
Random 5-3
Random profile 5-3
Range 5-16
Range Interpolation 5-14
Range Type 5-14
Ratio of gas-specific heats gas constant 5-71
Ratio shear modulus 2-13
Ratio Shear Modulus
Elastic Modulus 2-13
Rayleigh damping 5-55
Read from Flange File 3-19
Reduced intersection 2-27
Reduced Intersection 2-27
Reducers 3-21
References 6-34, 6-43, 6-79
Refractory lined pipe 3-8
Reinforcing pad 3-25, 3-55
Relief
Exit piping 5-75
Valve 5-5
Relief load
Analysis 5-69
Relief load synthesis for gases greater than 15 psig
Synthesis 5-69
Relief Load Synthesis for Gases Greater Than 15 psig
5-69
Relief load synthesis for liquids 5-74
Relief Load Synthesis for Liquids 5-74
Relief Valve or Rupture Disk 5-75
Relief valve or rupture disk Relief
Valve 5-75
Relief valve thrust load analysis
Valve thrust load analysis 5-69
Relief Valve Thrust Load Analysis 5-69
Remove HA Elements 8-23
Remove password 2-30
Remove Password 2-30
Replace 4-10
Required Data Set 9-6
Required Error Data 9-5
Required for Execution 9-3
Required Printer/ Listing 9-9
Resetting element strong axis - angle, orient 4-29
Resetting Element Strong Axis - ANGLE, ORIENT
4-29
Re-setting loads on existing spring hangers 3-51
Re-setting Loads on Existing Spring Hangers 3-51
Response Factor R (ASCE) 3-65
Response Spectra / Time History Load Profiles 5-13
Response spectra profiles 5-13
Response spectrum 5-16, 5-44
Response Spectrum / Time History Profile Data Point
Input 5-16
Restrained Piping per B31.8 3-87
Restrained weight 3-50, 6-9
Restrained weight case 6-9
Restrained Weight Case 6-9
Restraint
Auxiliary field 3-40
Loads 5-67
Restraints 2-17, 3-39
Re-use last eigensolution 5-57
Re-use Last Eigensolution 5-57
Review existing units file 7-10
Review Existing Units File 7-10
Reynolds number 6-29
Rigid
Element application 6-2
Elements 3-16, 3-119
Fluid weight Rigid
Fluid weight 6-2
Insulation weight Rigid
Insulation weight 6-2
Index 17
Material weight Rigid
Material weight 6-2
Modes 5-51
Rod 3-48
Support displacement criteria 3-48
Y restraints 3-50
Rigid Element Application 6-2
Rigid Elements 3-16
Rigid Fluid Weight 6-2
Rigid Insulation Weight 6-2
Rigid Material Weight 6-2
Rigid Support Displacement Criteria 3-48, 3-115
Rigids 2-17
Rod increment (degrees) 2-6
Rod Increment (Degrees) 2-6
Rod Tolerance (degrees) 2-6
Rod tolerance (degrees)Rod tolerance 2-6
Rotate 3-131
Rotation rod 3-42
Rotational option 3-119
rp/do 3-33
Run control data spreadsheet 3-49
Rupture disk 5-75
Rupture disk opening 5-75
Rx (cosx, cosy, cosz) or Rx (vecx, vecy, vecz) 3-42
RX (cosx, cosy, cosz) or RX (vecx, vecy, vecz) 3-42
Rx, Ry, or Rz 3-41
RX, RY, or RZ 3-41
S
Sa at 0.2 Seconds (NBC) 3-70
Sc 3-73
SC 3-73
Schneider 2-28
Scratch 9-16
Seam-welded 3-7, 3-16
Seam-Welded 3-7, 3-16
Seawater Data 6-34
Secid 4-15, 4-24, 4-26
SECID 4-15, 4-24, 4-26, 4-28
Section 1-Entity Information 8-14
Section 2-Segment Information 8-15
Section 3-Final CAESAR II Data 8-18
Section ID 4-15
Section identification - secid 4-15
Section Identification - SECID 4-2, 4-15
Section modulus calculations 3-15
Segment information 8-15
Seismic
Anchor movements 5-44
Loads 5-44
Zone 6-20
Zone coefficient 6-20
Seismic Zone (CFE) 3-67
Set/change password 2-30
Set/Change Password 2-30
Setting
Defaults Setting
Defaults 4-17
Nodes in space 4-17, 4-18
Setting Defaults - DEFAULT 4-2, 4-17, 4-22, 4-26
Setting Nodes in Space - NODE, NFILL, NGEN 4-18
Setting up the spring load cases 6-10
Setting Up the Spring Load Cases 6-10
Setup option 3-131
Sh 3-75
SH 3-75
Sh fields 3-73
Shadow Mode 2-18
Shape 4-47
SHAPE 4-47
Shear modulus of elasticity 3-10, 3-122, 4-14
Shock displacement 5-48
Shock load case 5-44
Short range springs 3-49
Should CAESAR II Size the Vent Stack (Y/N) 5-72
Should CAESAR II Size the Vent Stack (Y/N) 5-72
Show Informational Messages 3-98
SIF 3-10
SIF at bend 2-24
SIF Scratchpad 3-31
SIFs & tees 3-23
SIFs & Tees 3-23
SIFs and stresses 2-23
SIFs and Stresses 2-23
SIFs/Tees 2-17
Simplified ASME Sect. VIII Div. 2 Elastic Nozzle
Analysis 6-39
Single
Directional restraint 3-48
Element insert 3-93
Gimbal expansion joint 3-112
Hinged expansion joint 3-112
Unrestrained expansion joint 3-111
Sinusoidal forms 5-41
Site Class (ASCE) 3-66
Site Class (NBC) 3-69
Slipon 3-111
Slug flow 5-5
Smooth Transitions 2-18
Snubbers 5-37
Socket Fillet Weld Leg Length 3-102
Soil factor 6-20
Soil Type (CFE) 3-68
South African 1992 database 4-66
South African 1992 Database 4-66
Spatial
Combination method Spatial
Combination method 5-58
Components 5-58
Spatial Combination Method (SRSS/ABS) 5-58
Spatial or modal combination
18 Index
Combination method 5-58
Spatial or Modal Combination First 5-58
Special execution parameters 3-62, 3-118, 6-2
Special Execution Parameters 3-118
Specific gravity 3-11
Specified Minimum Yield Stress 3-83
Spectrum 2-6
Spectrum /Time History Profile 5-19
Spectrum analysis 5-44, 5-55
Spectrum Analysis 5-44
Spectrum Time History 5-31
Spectrum/time history profile 5-19
Spring
Design requirements 6-9
Forces 3-111
Rate 3-51, 6-10
Tables 3-45
Spring Design Requirements 6-9
Spring Forces 3-111
Spring hangers 3-51
Spring Rate and Cold Load 3-51
Square root of the sum of the squares 5-58, 5-61
Square Root of the Sum of the Squares (SRSS) 5-61
Standard airy wave theory 6-27
Standard structural element connections - beams,
braces, column 4-34
Standard Structural Element Connections - BEAMS,
BRACES, COLUMNS 4-34
Start node 5-10, 5-12, 5-20, 5-35
Start Node 5-10, 5-12, 5-20, 5-35
Starting frequency 5-7
Starting Frequency 5-7
Starting Node Number 8-23, 8-56
Static
Earthquake loads 6-20
Load case 5-49
Load case builder 6-22
Load case for nonlinear restraint status Static
Load case 5-49
Output processor 5-67
Seismic loadsStatic
Seismic loads 6-20
Superposition 6-17
Thermal criteria 5-67
Static Analysis Fatigue Example 6-46
Static friction coefficient 3-43
Static Load Case for Nonlinear Restraint Status 5-49
Static Seismic Loads 6-20
Static Seismic Wizard 3-65
Steel 2-17
Stif 3-42
Stiffness 3-42, 5-37
Stiffness factor for friction 5-50
Stiffness Factor for Friction (0.0 - Not Used) 5-50
Stiffness matrix 5-41
Stokes 5th order wave theory 6-25
STOKES Wave Theory Implementation 6-28
Stop node 5-10, 5-12, 5-36
Stop Node 5-10, 5-12, 5-20, 5-36
Straight pipe 3-25
Stream function wave theory 6-25
Stream Function Wave Theory Implementation 6-28
Stress
Calculation 3-84
Cycles 3-77
Intensification factors 3-14, 3-29
Intensity 6-36
Stress Concentration Factors 3-38
Stress intensification factor scratchpad 10-9
Stress Intensification Factor Scratchpad 10-9
Stress intensification factors (details) 3-29
Stress Intensification Factors Details 3-29
Stress stiffening due to pressure 3-121
Stress Stiffening Due to Pressure (all codes except
IGE/TD/12) 3-121
Strong axis moment of inertia 4-16, 4-49
Structural
Classification options 6-22
Database Structural
Database 2-9
Databases 4-49
Element keywords 4-2
Elements 4-46
Structural Data 9-13
Structural Database 2-9
Structural Databases 4-49
Structural Group (CFE) 3-67
Structural Steel Modeler 1-2, 4-1
Sturm sequence 5-63
Sturm Sequence Check on Computed Eigenvalues
(Y/N) 5-63
Sturm sequenceSturm sequence 5-63
Subsonic velocity gas conditions 5-74
Subsonic vent exit limit Subsonic vent exit 5-74
Subspace size 5-65
Subspace Size (0-Not Used) 5-65
Supply header 5-75
Supply header pipe wall thickness 5-75
Supply Header Pipe Wall Thickness 5-75
Supply overpressure 5-75
Supply Overpressure 5-75
Sustained
Analysis 6-16
Stress 3-84, 6-17
Stress limit 3-82
Sustained stresses and non linear restraints 6-17
Sustained Stresses and Nonlinear Restraints 6-17
Swedish Method 1 and 2 6-99
Sy 3-82
Sy - Yield Stress at Temperature 3-81
Sy data field 3-73
SYC, SY1-SY9 3-19
System
Index 19
Damping 5-55
System Design Factor 3-92
System directory name
Directory name 2-9
System Directory Name 2-9
T
T/Th/T'b 3-33
Tangent intersection point 3-14
Tank node number 3-56
Tank Node Number 3-56
Tapered transitions 3-25
Target Stress 3-135
TD/12 Modulus Correction 3-87
Te/Tb 3-33
Technical discussion of liqt interface 8-76
Technical Discussion of LIQT Interface 8-76
Technical Discussion of the PIPENET Interface 8-80
Technical Discussions 1-2, 2-3, 6-1
Technical notes on CAESAR II Hydrodynamic
Loading 6-29
Technical Notes on CAESAR II Hydrodynamic
Loading 6-29
Tee SIF Scratchpad 3-98
Temperature 3-8, 7-16
Temperatures 3-8
Ten Percent Method 5-60
Text Options 2-19
The Right Hand Rule 6-113
The Structural Steel Property Editor 4-3
Theoretical cold load 3-51, 6-10
Thermal
Bowing 2-15
Bowing delta temperature 3-120
Expansion coefficient 2-3, 2-12, 3-8, 3-84, 3-121
Expansion/pipe weight report 6-2
Shakedown 6-5
Thermal Bowing Delta Temperature 3-120
Thermodynamic entropy 5-74
Thermodynamic Entropy Limit /Subsonic Vent Exit
Limit 5-74
Thickness 2 3-22
Thrust 3-21, 5-69
Thrust at the end of the exit piping 5-76
Thrust at the End of the Exit Piping 5-76
Thrust at the end of the manifold piping 5-76
Thrust at the End of the Manifold Piping 5-76
Thrust at the vent pipe exit 5-73
Thrust at the Vent Pipe Exit 5-73
Thrust at valve pipe/vent pipe interface 5-73
Thrust at Valve Pipe/Vent Pipe Interface 5-73
Tied 3-112
Tied single expansion joint 3-112
Tied universal expansion joint 3-112
Time 5-18, 5-48
History analysis 5-5, 5-48, 5-55
History animation Time
History animation 2-21
History loads 8-76, 8-80
History Time
History analysis 5-48
Step 5-54
Time History 5-48
Time History Animation 2-21
Time history load cases 5-19
Time history profile data point 5-16
Time history profiles
History load profiles 5-13
Time history time step 5-54
Title page 3-113
Title Page 3-113
To 3-2
TO 4-20, 4-23, 4-25, 4-27, 4-30, 4-32, 4-43, 4-46
To node number 3-2
Toolbar buttons 1-1
Tools
Material database 7-14
Multiple job analysis 7-7
Top 2-17
Topographic factor parameters 6-22
Torsional
Stiffness 6-7
Torsional R 4-16
Torsional spring rates 3-110
Torsional Spring Rates 3-110
Transforming from Global to Local 6-129
Transient 5-73
Load 5-44
Load cases 5-48
Transient pressure rise on valve closing 5-73
Transient Pressure Rise on Valve Closing 5-73, 5-76
Transient pressure rise on valve opening
Pressure 5-73
Transient Pressure Rise on Valve Opening 5-73, 5-76
Translational
Option 3-119
Restraint 3-42
Stiffness 3-109
Transverse stiffness 6-7
T-univ 3-112
T-UNIV 3-112
Type 3-14, 3-40
Type field 3-14
U
UBC 5-13
UK 1993 database 4-68
UK 1993 Database 4-68
UKOOA 3-10, 6-106
Ult Tensile Stress 7-17
20 Index
Ultimate tensile strength 3-82
Umbrella fitting 5-71
Unbalanced pressure force 5-3, 5-67
Underlying Theory 6-60
Uniform
Building code 5-13, 5-56
Load 4-44
Loads-UNIF 4-43
Support excitation 5-44
Uniform load in g's 3-121
Uniform Load in G's 3-62, 3-121, 4-2, 6-20
Uniform loads 3-62
Uniform Loads 3-62
Uniform loads - unif 4-43
Uniform Loads - UNIF 4-43
Units
Conversion Data 8-72
Units conversion data 8-72
Units Conversion Data 8-72
Units File 4-3
Units file name
File name 2-10
Units File Name 2-10
Units file operations
File operations 7-10
Units File Operations 7-10
UNITS Specification - UNIT 4-2, 4-11
Units specification - Units
Specification - UNIT 4-11
Unskew 3-131
Untied 3-111
Untied universal expansion joint 3-112
Update history 1-1
Update History 1-2, 10-1
Use Background Color 2-16
Use FRP Flexibilities 2-13
Use FRP SIF 2-13
Use Out-Of-Core Eigensolver (Y/N) 5-66
Use PD/4t 2-28
Use Pressure Stiffening on Bends 2-6
Use Schneider 2-28
Use WRC 329 2-28
User ID 2-22
User IDUser ID 2-22
User-defined 4-15
User-Defined 4-15
User-defined SIFs anywhere in the piping system 3-
29
User-Defined SIFs Anywhere in the Piping System 3-
29
User-defined spectra 5-44
Using Local Coordinates 6-120
Utilities 4-48
UTS - Ultimate Tensile Strength of Material 3-81
UTSa - Ultimate Tensile Strength at Ambient
Temperature - TD/12 3-86
U-univ 3-112
U-UNIV 3-112
Ux, Uy, Uz 4-44
UX,UY,UZ 4-44
V
Valve
/Flange database 2-10
Pipe/vent pipe interface 5-73
Valve / Flange Data File Location 2-10
Valve orifice gas conditions
Orifice gas 5-74
Valve Orifice Gas Conditions /Vent Pipe Exit Gas
Conditions/Subsonic Velocity Gas Conditions
5-74
Valve/flange database 3-94
Valve/Flange Database 3-17, 3-94
Valves and flanges 2-10
Valves and Flanges 2-10
Velocity vector 5-41, 5-48
Vent
Pipe exit 5-73
Stack 5-72
Vent pipe exit gas conditions
Pipe exit gas 5-74
Version and job title information 8-57
Version and Job Title Information 8-57
Vertical Axis 4-4
Vessel
Diameter 3-55
Material number 3-55
Node 3-53
Node number 3-55
Temperature 3-55
Type 3-59
Wall thickness 3-55
Vessel centerline direction cosines 3-59
Vessel Centerline Direction Cosines 3-59
Vessel centerline direction vector x, y, z 3-55
Vessel centerline direction vector X, Y, Z 3-55
Vessel Diameter 3-55, 3-59
Vessel Material No. (Optional) 3-55, 3-59
Vessel Node Number (Optional) 3-55, 3-58
Vessel reinforcing pad thickness 3-55
Vessel Reinforcing Pad Thickness 3-55, 3-59
Vessel Temperature (Optional) 3-55, 3-59
Vessel Type - Cylinder (0) or Sphere (1) 3-59
Vessel Wall Thickness 3-55, 3-59
Vibrations 5-41
Video Driver 2-18
View/edit file 7-12
View/Edit File 7-12
Visibility % 2-18
Von Mises theory 2-28
Vortex shedding 6-22
W
Wall thickness 2-5
Index 21
Wall Thickness of Matching Pipe 3-106
Wall thickness/schedule field 3-7
Wave
Data 6-33
Theories 6-26
Wave Data 6-33
Wave Loads 3-64
B1 3-27
Weak axis moment of inertia 4-16, 4-49
Weight analysis 3-50
Weight Units 8-24
WELD (D) 3-26
Weld d (Mismatch) 3-100
Weld ID 3-25, 3-26, 3-37, 3-100
Welded 3-111
Width to Height Ratio 3-136
Wind
Effects 5-3
Exposure options 6-22
Force 6-22
Load 3-8
Loads 4-46, 6-22
LoadsWind
Loads 6-22
Pressure 6-22
Shape factor 3-64, 4-46, 6-22
Speed 6-22
Wind / Wave Loads 3-63
Wind Loads 3-63, 6-22, 6-23
Wind Loads - WIND 4-2, 4-46
Wind Shape Factor 3-63
Wind/wave loads 3-63
+Mill Tol % 3-7
Wl for Bends 3-16
Wn 3-111
WN 3-111
WRC 107 2-7, 6-37
WRC 297 10-9
WRC 297 Local Stress Calculations 10-9
WRC 329 2-28, 6-12, 6-81
WRC-107 Interpolation Method 2-7
WRC-107 Version 2-7
Wt/sch 3-7
Wt/Sch 3-7
X
X (cosx, cosy, cosz) or X (vecx, vecy, vecz) 3-42
X , Y, or Z 3-41
X, Y, or Z 3-41
X2, Y2, Z2 3-41
Xrod (cosx, cosy, cosz) or Xrod (vecx, vecy, vecz) 3-
42
XROD (COSX, COSY, COSZ) or XROD (VECX,
VECY, VECZ) 3-42
Xrod, Yrod, Zrod 3-42
XROD, YROD, ZROD 3-42
XSNB, YSNB, ZSNB 3-41
XSPR, YSPR, ZSPR 3-41
Y
Yield
Criteria theory 2-28
Strength 4-14
Stress
Stress 2-28, 7-17
Yield Stress 7-17
Yield Stress Criterion 2-28
YM 4-13
Young's modulus of elasticity 4-13
Ys 4-14
YS 4-14
Z
Z-Axis Vertical 2-15, 3-123, 4-12
Zero
Period acceleration 5-44
Weight rigids 6-2
Zero Length Expansion Joints 3-20
Zero-length expansion joints 3-20
ZPA (Reg. Guide 1.60/UBC- G's)/# Time History
Output Cases 5-56
ZPA time history output cases 5-56
CAESAR II
TECHNICAL REFERENCE
VERSION 5.20
LAST REVISED 9/2009