Conclusions - CAESAR II - Reference Data

CAESAR II Applications Guide

English (United States)
Search by Category
Reference Data

The review of piping stresses shows that the piping has adequate wall thickness and support to keep within the sustained allowable stress, as well as enough flexibility to remain below the expansion allowable stress limit. A quick review of the system displacements does not reveal any interference problems from pipe expansion.

Equipment loads

Equipment loads must still be checked to ensure a safe and effective design. The pump loads at node 5 may be compared to the API (American Petroleum Institute) Standard 610 (Seventh Edition, February 1989), Centrifugal Pumps for General Refinery Service. The nozzle loads, too, can be compared to the allowed maximum limits. The nozzle loads can be translated into local stresses using Welding Research Council Bulletins 107 or 297 - Local Stresses in Cylindrical Shells Due to External Loadings on Nozzles (WRC 107) or it's Supplement (WRC 297). These local stresses can then be compared to allowable stress values established in ASME Section VIII Division 2 Appendix 4, Mandatory Design Based on Stress Analysis.

Because the loads on these boundary conditions are related to the piping system layout, the piping system cannot be properly approved until these load limits are also verified. These verifications are performed in Tutorial B.


Final reports should now be made to document this design. The input listing can be generated from Classic Piping Input or from the Static Output Processor. You should include the current status of the software’s default settings in this input echo and a hard-copy of a few input plots. Structural and stress results from the Static Output Processor substantiate the current design.

Archive the files Tutor-A.C2 and Caesar.cfg to preserve a copy of the CAESAR II input, load case definition, output, and software default settings. Often upon release of a new version of CAESAR II, archived files must be converted to the new version and subsequently re-analyzed. This is primarily due to changes within CAESAR II as new features and codes are added. To avoid this, keep the old version of the software available, and use newest version for new analyses.