Applies To | |
Product(s): | AutoPIPE |
Version(s): | ALL; |
Area: | Results |
Date Logged & Current Version | Oct. 2017 11.01.00.23 |
Model Definition |
The model taken is a pump system where Pump A(Point 1) or Pump B(Point 90) or both Pump A and B are in operation. The point 170 is connected to a vessel oriented in Z axis and at this point we enter a flexible anchors(by CAESAR under the WRC297 and by AUTOPIPE under user flexibility)
Pipe OD at Pump A or B | 168.3 mm | ||
Wall Thickness at Pump A or B | 7.1 mm | ||
Pipe OD after the reducer | 219.1 mm | ||
Wall Thickness after the reducer | 8.2 mm | ||
Temperature for the pump in Operation | 450 degC | ||
Temperature for spare Pump | 80 degC | ||
Material | A106B | ||
Piping Code | B31.3:2006 | ||
Allowable Stress at 80 degC | 137.89 N/mm2 | ||
Allowable Stress at 405 degC | 86.29 N/mm2 | ||
Pressure | 10 bar | ||
Earthquake Loading |
AutoPIPE Load case 2 - E2 Load case 3 - E3 Load case 4 - E4 |
caesar U2 U3 E1= U1+U2 (CAESAR) | |
Wind Loading |
Number of load cases : 4 Ground elevation for wind : 0.00 mm Load case 1 - W1 Load case 2 - W2 Load case 3 - W3 Load case 4 - W4 User defined wind profile | ||
Valves between 10-15,15-20,70-75,75-80 Nodes Weight | 5000 N each | ||
Reducer between 1-5,85-90 Nodes OD1/WT1 OD2/WT2 |
. | ||
Welding Tee | Node point: 45 | ||
Elbow Radius 1.5 OD=304.8 mm | Node points: 25,40,50,60,65,105,115,120,130,140,150,155 | ||
Spring Hanger |
Node Point 20: Stiffness Rate:133N/mm ,Cold load:14083 N | ||
V-Stop(+Y support) |
Node points: Support Friction=0.3 | ||
Line Stop (Stop in X direction) simulated by an incline support |
Node point: Support Friction=0.3 | ||
Flexible Nozzle AutoPIPE used User Flexibilities |
Node point: Vessel Axis = Global Z | ||
Thermal Anchor Movements: |
Node point: Case T1: DY = 2.35mm, Case T3: DY = 2.35mm |
AutoPIPE | caesar |
Support Rigid Stiffness Anchors Rigid Stiffness Default Friction Stiffness: 1.7512e+10 N/mm AUTOPIPE does not allow you to change the friction stiffness but the friction tolerance is used to check analysis convergence. |
Support or Anchors Stiffness Friction Stiffness: 4.38e+006 N/mm The friction stiffness, the friction angle variation, the friction slide multiplier and the coefficient of friction are able to be set in the configuration file. |
AutoPIPE | caesar |
AutoPIPE assumes that a valve is 100 times stiffer than the connecting pipe material at the start of the valve. The Surface Area Factor is the factor used to multiply the insulation weight of the pipe per units length to get the insulation weight of the valve per units length. To simulate the rigid element like CAESAR II , the valves are going to be modeled like an element with 10 times the wall thickness of the pipe and we will have to correct the weight entered(5000 N) because in this case the weight per meter is much bigger. PIPE3 is the pipe with 82 mm wall thickness. The weight of the pipe total =3170 N/m The weight of the check valve(533 mm) to be entered should be : The weight of the check valve(419 mm) to be entered should be : The insulation density has been changed from .2 Kg/dm3 auf 1.75 x .2=.35 Kg/dm3 |
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 weight of insulation added is equal to the same weight that would be computed for an equivalent straight pipe times 1.75 and cannot be changed. According to CAESAR II Miscellaneous Data The element 533 has a total weight of That means a weight of 5368.9 N The element 419 has a total weight of That means a weight of 5289.8 N |
Post Processing Load Case (Non-linear) |
AutoPIPE | caesar |
GR(1)=GR+MaxP(1) GR=Weight |
L13=W+P1+H -W=Weight |
Operating loading cases are only to check the displacements & forces and moments
AutoPIPE | caesar |
GT1(1)=GR(1)+T1(1) T1(1)=Temperature 1 for analysis set 1 |
L2=W+D1+T1+P1+H T1=Temperature 1 |
Operating loading cases are only to check the displacements & forces and moments
AutoPIPE | caesar |
Amb to T1(1) Thermal expansion from Ambient temperature to T1(1),T2(1),T3(1) |
Exp1=L2-L13 |
The combination is done by summation of the absolute value of each term at the stress level
AutoPIPE | caesar |
E1 = in x and -1/2 x in y dir Dir = direction To be checked: SUS+E1 SUS = GR(1) +MaxP |
U1=in x dir U is for uniform load in g |
The combination is done by summation of the absolute value of each term at the stress level
AutoPIPE | caesar |
W1 = Wind in X dir To be checked: SUS+W1 A User Profile is going to be given (a Pressure per elevation) |
WIN1=Wind in X dir A User Profile is going to be given (a Pressure per elevation) |
The Units File |
AutoPIPE | caesar |
By Autopipe you can create your own units file but you have to define your own conversion coefficients. The basic is the English units(English.unt) and we have created a metric units file called CAESAR.unt) The Units file to be used is set under: General Model Options dialog A different units file for the input and output can be set. If you need to change the units, you can always go back to General Model Options dialog and change it. AUTOPIPE.unt are set per default in English units. If you change the name for instance SI.unt into AUTOPIPE.unt. The default unit is going to be SI. |
By CAESAR II you can as well create your own units but the conversion factors are already calculated for you and you only need to choose the units you want. The basic calculation is as well done in English units. The units file is called for instance FUCHS.fil and have to be stored into the system directory from CAESAR II to be able to be used on all calculations. Once you set by the CAESAR.CFG the default units file, the input you create is set to these units. To get other units by the output, you only need to change the units in the configuration file after that. It is always possible to change the input units By using CAESAR Tools/convert Input to new units |
The Configuration File |
AutoPIPE | caesar |
Edit Model options Dialog. |
The configuration file from CAESAR II is located in the working directory and not attached to the input file. That means that it is a common file from a certain directory. The main disadvantage is that if you change anything in this config because of a certain input and you rerun another input under this directory, the results are going to be changed.. |
Analysis Loading Definition |
AutoPIPE | caesar | ||||
AUTOPIPE static analyses by load increments. It is important to note that in an AUTOPIPE analysis, each load case is an increment of load, not a total load as in Caesar. For a linear analysis, the results for each load case are obtained all at once and the “Gaps/Friction/Soil" option has to be disabled. For a nonlinear analysis the results are obtained sequentially. Non-Linear load increments, the steps are: 1-Analyze for Gravity; then The “Static analysis set” is set under Loads/Static Analysis Set Note: Ignore Friction E and Ignore Friction GR options have to be unchecked since CAESAR II the friction is always acting The code and non-code combinations are created automatically and we can define as many analysis sets up to 999 and combine the results as we want. User non-code combinations can be created and typically used to create operating cases to examine maximum forces and moments on equipment nozzles and supports or anchors. Note: The hydrotest is a linear analysis and typically defined in a 2nd analysis set to define this case. GT1=GR+T1 -> Operating 1 by CII We have as well to define operating 1 + Wind1 by the non-code combination to define the maximum forces and moments on supports. Load Combinations can be selected for printing |
CAESAR II is performing analyses for total loads. That means that CAESAR II is throwing every item (Weight, displacements, Temperature and so on) in a basket and adds everything together regardless when it happens. If analyses are performed for total loads, the steps are: 1-Analyze for gravity(Weight) The loading cases will look like: L1=W+P1(SUS) SUS= sustained To sum up ,you can find following annotations
By the load case editor, you can define the type of loading. To notice that the basic allowable stresses taken are set by the stress type: SUS -> sustained stress against Sh This is activated by the CAESAR II Config. OPE -> there is no stresses check, it is only valid to check the forces and moments. It is important to notice that first the basic loading cases are defined, then their combinations It is always possible to save the loading cases to be able to reuse it on other input. In the load case options , you can define the output statut: which allows you to specify whether or not you will be able to check the loading case. Output type: To define on which level your combination is going to be (at diplacement/force/stress or at Dipl/force or Disp/stress or force/stress or disp or force or stress). Combination method: Algebraic ,Scalar ,SRSS ,Abs ,Max ,Min ,SignMax ,SingMin Snubbers: active or not active Hanger stiffness: Rigid, Ignor ,as design Elastic Modulus: Ec or Eh Friction multiplier: to turn on(1) or off (0)the friction With our example having 4 loading cases in Static earthquake and 4 wind directions,we end up having already 36 loading cases defined with the friction on.As the friction is not always acting,we should do the same loading cases without friction. CAESAR II loading became quite complicated For the wind load, we define the wind pressure per elevation or use other codes. |
Input Check |
Results Comparison |
Comparison of Sustained and Thermal Forces and Moments |
1. With +ve % difference results are CAESAR II bigger than AUTOPIPE. On 28 results, 23 cases CAESAR II gives higher Forces and Moments.
When the difference is above 6.6 % ,it is always the case that CAESAR II is calculating higher forces and moments. The maximum difference is 24.2%.
2. AutoPIPE has a more advanced non-linear analysis engine with load sequencing and we can expect a more accurate non-linear results than CAESAR
To get CAESAR II to make analysis linear, set the restraints as Y instead of +Y supports at node points: 110 ,125,135, and 140. If enter as +Y, the supports are non linear. The friction by the loading cases are set to zero.
That means that you cannot do a linear analysis on the same input. We have to create a separate input to set up the conditions for non-linear analysis.
AUTOPIPE is able on the same input to have non-linear and linear analysis because it can create a new analysis set with the linear conditions.
Comparison of Occasional Loads in T1 temperature case |
1. With +ve % difference results are CAESAR II bigger than AUTOPIPE. On 32 results, 23 cases CAESAR II gives higher Forces and Moments.
One result, AUTOPIPE is bigger than CAESAR II ,we have a difference of 17%. Otherwise in most cases CAESAR II is calculating higher forces and moments with a maximum of 19.3%
2. AutoPIPE has a more advanced non-linear analysis engine with load sequencing and we can expect a more accurate non-linear results than CAESAR
1. The Linear Results are consistently under 5% difference, with only one result at 6.1 %
CONCLUSION |
To provide specific answer to even a slightly complex system differences like the system at hand would require all the assumptions and methods adopted in both the applications completely, which is not practical.
Comparing results between two applications is always tricky and are bound to be different apart from very simple cases. Although the basic theory and assumptions behind the two applications may be the same, but as the products evolve the different components may start to diverge slightly based on selected options. These divergences may compound when the models depart from being very simplistic models.
For example, if you run very simple cantilever models in both the applications with a tip force applied, you will get exactly the same results:
Length of pipe (ft) |
Free end force (lbf) |
AP Displacement (in) |
CII displacements (in) |
0.5 |
10,000 |
0.0008 |
0.0008 |
1.0 |
10,000 |
0.0021 |
0.0021 |
2.0 |
10,000 |
0.0085 |
0.0085 |
5.0 |
10,000 |
0.0946 |
0.0946 |
10.0 |
10,000 |
0.7135 |
0.7135 |
This could tell us that both the applications are using the same beam theory with shear deformation included. When we depart from simplistic models then some assumptions / implementations like below may come in to play:
On individual level, there may be slight differences in these formulations. However, when the whole system is analyzed, the differences may get compounded due to interaction of these individual differences. One can trust any application if one understands the assumptions involved in the solution and understands that the results are a fair approximation of the actual system. Some applications may have a better representation of a particular component / analysis, while the other may be good in another area.
A good way to gain more confidence in to any application results is to start with simple models, perform a few tests on the component / analysis, and confirm that the results simulate the actual system reasonably well. AutoPIPE QA program backs up the results generated by the program with a rigorous set of hand calculations and published results.
To sum it up, AUTOPIPE has a more advanced non-linear analysis engine with load sequencing and we can expect a more accurate non-linear results than CAESAR II. Caesar non-linear results are consistently higher than AutoPIPE. By the comparison, the maximum differences for Stresses and Displacements was 5.1 %.
See WIKI here for typical reasons why results may be different.