Applies To
Product(s):	AutoPIPE
Version(s):	ALL;
Area:	Modeling
Date Logged & Current Version	June 2022 12.08.00.063

Problem:

Limitations of inserting a model from STAAD into AutoPIPE using PipeLInk.

Solution:

With the use of PipeLink, an advanced structural model data exchange, model data can be exchanged between STAAD.Pro and AutoPIPE.  PipeLink provides a plug-in interface in STAAD.Pro for the exchange of structural information, e.g. structural geometry, boundary conditions, load information, and displacement information to an intermediate database file (*.pipelink), which can then be read by AutoPIPE.  The process of inserting a model from STAAD.Pro into an existing AutoPIPE model is described below.

 As of June 2022, AutoPIPE 12.08:

Imported STAAD Information

• • PipeLink revision information
  • Model information
  • Piping Geometry as an ADI
  • Pipe Supports
  • Pipe Support Connections
  • Supports
  • Support Loads
  • Anchors (including connecting anchors)
  • Anchor Loads

Limitations

1. Member loads cannot be imported for beams.

2. Import Imposed Point Dead Loads

• • • Only the loads with the type 'DEAD' mentioned in the STAAD database will be imported. all other loads are ignored.
    • In the case where a negative weight is encountered, it will be converted to a zero value and a warning message will be issued mentioning this change.
    • All offset values (DX, DY, DZ) for additional weights will be zero.

3. Unsupported beam sections will be imported as Non-Standard and drawn as an I-beam.

Unsupported sections are those where only STAAD has the functionality to create and analyze such sections (ex. tapered sections, user defined sections, etc.. ) , but not currently available in AutoPIPE (June 2022). Only being able to define the section is not enough. AutoPIPE would then need the capability to be able to analyze these sections as well. This ability will be added to AutoPIPE in a future version after ISM in STAAD.

4. As of AutoPIPE 9.6, multiple models from multiple PipeLink files can now be inserted.

5. When importing beam releases, AutoPIPE is limited to three degrees of freedom, i.e. axial (translation), Y-Y and Z-Z (rotational).  Moreover, AutoPIPE cannot handle partial beam releases.  Therefore, any beam releases that do not fall into those degrees of freedom, or are partially released, will be ignored.

6. Any changes in structural nodes and members are not exported and will be lost on a subsequent import.

7. Material Name is appearing empty. AutoPIPE allows for maximum of 16 characters, whereas STAAD allows for more than 16 characters. Workaround for material name issue is to have 16 characters at max for material name in STAAD. 

8. Beams with same name in a subsequent import will be renamed to 1.2, 2.2, 3.2 respectively

9. Delete > Structure > Structural Model, The following will be removed from the model

• • • Beams and associated nodes that were created in AutoPIPE or imported via PipeLink
    • X Section IDs and Material Data (Standard and user-defined)
    • Anchors placed on beams
    • Supports placed on beams, except the ones connected to piping points
    • Xtra Data and loads defined on beams and beam nodes, including Point Loads imported via PipeLink
    • Imposed displacements on supported piping points imported using PipeLink
    • Subsequent export using PipeLink would not have any previous revision record, unless an import has been performed

10. Only individual load cases are imported from STAAD. 

Structural codes require specific code combinations, while Piping codes have their own distinct code combinations. Although some fundamental combinations may overlap between the two, a significant number of combinations are unique to each type of analysis (Structural vs Piping). Consequently, it is advisable for the user to focus solely on the appropriate combinations relevant to each application, rather than attempting to manage all combinations from both applications in each other analysis.

Attempting to handle all combinations across both applications by adding user combinations can be quite challenging and may exceed the capability of the application.

See Also

Export Model to STAAD Using PipeLink (*.pipelink)

Bentley AutoPIPE