Professional Documents
Culture Documents
Sap 2000 Vs Staad Pro
Sap 2000 Vs Staad Pro
STAAD PRO
Introduction To Piperack Modeling in SAP2000
This brief introduction to SAP2000 is intended for STAAD Pro users wishing to make the transition to
SAP2000. It is focused exclusively on steel design.
The primary focus is to highlight the main areas where SAP2000 workflow will differ from STAAD Pro.
Member Geometry
Defining member geometry in SAP2000 can be much simpler compared to STAAD Pro. SAP2000 allows
for intermediate joints within a continuous member, automatically calculates length adjustment factors
in cases where a continuous member is divided, and automatically calculates effective length factors for
columns based on the structure geometry.
The highlighted frame member in Fig.1 is one continuous member, despite having an intermediate joint
where the bracing connects. In contrast, STAAD Pro would treat this member as two separate beams.
This functionality in SAP2000 results in the following:
Fig.2 shows the same structure as Fig.1, with the beam in question divided into two, at the joint with the
bracing. The steel section properties for one of the beam parts show that an L-factor of 2.0 is used in
moment design, to account for the full length of the member.
Similarly to the calculation of L-factors, SAP2000 will also automatically compute K-factors (effective
length) for columns based on end conditions and connectivity. SAP2000 documentation does mention
that K-factors tend to be conservative, so they should be checked after analysis is performed, and
overridden when necessary.
Defining loading in SAP2000
Defining loading in a SAP2000 model requires three steps: defining the load patterns, defining the load
cases, and defining the load combinations.
Load Patterns
Load patterns are simply a collection of loads. When defining load patterns, it’s possible to be quite
granular, thus making the model easier to understand. For instance, when applying piping loads to a
model, it may be beneficial to define a separate load pattern for each line in the system. The resulting
model would be self-documenting. Other users should be able to make updates to such a model with
minimal effort.
Load patterns for notional, wind and seismic loads have the option of defining lateral loads
automatically (with some limitations), according to various international codes.
Load Cases
Load cases in SAP2000 are a collection of one or more load patterns. Each contributing load pattern can
be further factored. Also, the load case definition allows the user to specify the type of analysis required
(linear or non-linear). Analysis in SAP2000 is performed on the load cases.
In Practice
A common complaint in STAAD Pro piperack models is bloated load combination definitions. Often one
comes across models with hundreds of defined load combinations. The root cause of this is having a
separate load combination for each of eight principal directions of the various lateral loads.
a. Define a load case for the eight directions for each lateral load. Say we consider wind loads,
we’ll have 8 load cases: E, NE, N, NW, W, SW, S, SE.
b. Define a general Wind load combination that combines the 8 load cases as an envelope. The
result will have a maximum and minimum member force for each member for the 8 load cases
together.
c. Define your design load combinations using the aggregate Wind combination.
Using this approach, a STAAD Pro model with 100+ design load combination can be reproduced in
SAP2000 with 20 design load combinations.
P-Delta in SAP2000
There are two methods that can be used in SAP2000 to perform P-Delta analysis:
The drawback of this approach is that non-linear load cases take longer to process, thus for a model with
many load cases the analysis time will increase significantly.
Initial Stiffness
An alternate approach is to define only one P-Delta load case in the model, with the assumed dead loads
applied. Other load cases in the model can then be configured as linear-static load cases, using the
stiffness matrix resulting from the P-Delta load case as an initial condition.
All input in SAP2000 needs to be entered using the graphical interface, or via input tables.
When defining model geometry using the graphical interface defining grid systems is a requirement, as
new members and joints can only be placed at grid intersections, or at existing joints.
Units in SAP2000
SAP2000 allows for switching units on the fly. The main SAP2000 window has a dropdown where the
input units for the model can be selected. Modifying the value in the dropdown immediately updates all
display screens with the newly selected units.
Additionally, most other input windows in SAP, such as the load definition window have their own unit
selection dropdowns. These are initially set to the units selected in the main window, but can be
changed on the as required.
Viewing Results
Upon performing an analysis in SAP2000, reactions, member forces and joint displacements can be
viewed for all load cases and combinations.
Performing a design check on the structure requires additional steps in SAP2000, once the structural
analysis is performed.
1. First, the design preferences, including the design code to be used, must be selected.
2. Second, the design combinations for strength check (and optionally displacement check) need to
be specified.
The results screen upon completion of the design check shows member section assignments, and color
codes the members based on utilization ratios. It’s important to note that this screen will not indicate
failures such as a failed slenderness check.
In order to view all possible failures in the model the appropriate output view must be selected.