Conclusions - CAESAR II - Reference Data

CAESAR II Applications Guide (2019 Service Pack 1)

Reference Data
11.0 (2019)

Piping stresses show that the pump discharge loads are now within their allowable limits.

Vessel loads

While not part of this tutorial, the vessel loads from the nozzle at node 40 should also be checked. Unlike loads on the pump, these loads cannot be compared to a fixed load limit. Instead, these loads must be converted to local stresses on the vessel and then compared with the limits defined by ASME Section VIII, Division 2. As a very rough guide for evaluating local vessel stresses, you can check the code defined stress on the pipe connected to the vessel. If those stresses are below about 6000 psi, the vessel stresses should be adequate. Looking at the operating, sustained, and expansion stresses at node 40, the maximum stress is less than 2500 psi. The vessel loads seem fine.

To check the stresses in detail, the Welding Research Council Bulletin 107 (WRC 107) can be used to convert the applied forces and moments to the appropriate local stresses. CAESAR II provides a processor to convert these loads into WRC 107 stresses and a second processor to combine the different stress categories (general or local primary membrane stress intensity, primary membrane plus primary bending stress intensity, and primary plus secondary stress intensity) for comparison with their design limits.


Final reports should now be made to document this design change. The input listing can be generated from Classic Piping Input or from the Static Output Processor. You should include the software's current 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-B3.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 reanalyzed. 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 to view existing analyses, and use the newest version for new analyses.