| Applies To | |
| Product(s): | AutoPIPE, |
| Version(s): | 2004, XM, & V8i |
| Environment: | N/A |
| Area: | Modeling |
| Original Author: | Bentley Technical Support Group |
Nov 2014, AutoPIPE V8i 09.06.01.10
Problem:
How to model multiple pipe connections to a single header in AutoPIPE?
OR
Answer:
Use the same modeling technique as used in the following AutoPIPE help section:
Help > Contents> Contents Tab> Modeling Approaches> Modeling Approaches> Vessels
In this cases above the user will need to manually locate the surface of the header where the pipe will actually be welded. When inserting a new pipe run users have the option to use Cylindrical or Cartesian from the start point to establish the 2nd node point on the run.
Procedure:
1. Move cursor to header pipe node point (ex. A05)
2. Convert Node into a Tee
3. Insert new branch segment (ex. B) on tee (ex. from A05), extend new piping to Pipe #1 connection location (ex. B01), should be on the outside surface of the header pipe.
4. Insert additional node points on segment piping as needed.
5. Select the piping inside of the header pipe (ex. A05 to B01). Insert> Rigid Options Over Range> Include Weight - OFF, Include Thermal Expansion - ON. press OK button to close dialog screen.
6. Select the header node point, Insert Xtra Data> Joint type and user SIF = user defined, "Override all SIF's at this point" - Checked ON.
7. Select node point on surface of pipe where the connection is made, (ex. B01), Insert Xtra Data> Joint type and user SIF, enter the correct SIF for the connection point, and again, "Override all SIF's at this point" - Checked ON.
8. Repeat steps #3 - #7 for each additional pipe to be connected at the same location (ex. A05).
9. Repeat steps as need along the length of the header.
Conclusion:
While the methods above is technically correct for modeling a branch on a vessel. There are some pros and cons to be aware of. The user should select the modeling approach that best suits their situation of pipe size and vessel size.
Pros:
Program will automatically calculate an SIF for each branch connection based on selected piping code
Cons:
The code SIF calculation does not take into consideration multiple branch connections in close proximity to one another. May want to analyze the connection in another application or hand calculations to get an overall SIF of the junction for both branches simultaneously
See Also
External Links
Bentley Technical Support KnowledgeBase
Comments or Corrections?
Bentley's Technical Support Group requests that you please submit any comments you have on this Wiki article to
the "Comments" area below. THANK YOU!