Page Comparison

{info}
This page is devoted to *frequently asked questions* (FAQ) related to [composite behavior|kb:composite behavior].
{info}

\\

{on-this-page}


h2. Why is unexpected response generated for a composite section?

*Extended Question:* I have two comparable models, described below, but Model 1 deflection is less than expected. Is there an explanation?

Model 1:

* Composite section with steel-girder [frames|kb:Frame] and concrete-deck [shells|kb:Shell].
* U1, U2, and U3 restraints assigned to either end of the girders.

Model 2:

* A single composite-section frame element created in the Section Designer.

*Answer:* The unexpected results of Model 1 may be attributed to its boundary conditions. The longitudinal restraints at either end of the girder are not located at the cross-section centroid, causing longitudinal force to act along a moment arm extending from the neutral axis. This behavior induces an additional moment which influences flexural response and vertical displacement. While kinematically correct, this behavior is different from that of Model 2 because of these boundary conditions.

The resultant axial force is the net effect of longitudinal stresses acting along the composite section. When longitudinal restraints are higher in the cross section, the neutral axis moves upward as well. To maintain equilibrium with the tensile forces located below the neutral axis (now greater because a larger portion of cross section is below the neutral axis), compressive forces are introduced at the restraints. These axial forces may be released with the assignment of a roller support at either end. This would allow axial force to transfer into longitudinal displacement.


h2. How are partially-composite sections modeled?

*Extended Question:* For a concrete-deck over steel-girder section that is 85% composite, will assigning a shell-element membrane-stiffness modifier of 0.85 simulate 85% composite action?

*Answer:* Given this design, composite-section stiffness is a function of three sources which include the following:

# Stiffness of the girder about its own center of gravity.
\\
\\
# Stiffness of the deck about its own center of gravity.
\\
\\
# Additional girder and deck stiffness contributions about the center of gravity of the entire section.

Changing the deck membrane modifier to 0.85 would directly affect the 1st source of stiffness, and indirectly affect the 3rd source. However, 85% composite action would allow some slip between deck and girder, therefore only the 3rd source of stiffness should be affected.

In a detailed model, where the deck and the girder explicitly modeled, the 3rd source of stiffness may be reduced using flexible [links|kb:Link] (rather than rigid or fixed) to connect the girder to the deck. The stiffness derivation for these flexible links would be based on model discretization and the prescribed 85% composite action.

Further, if a single frame element is used to model the composite section, the [stiffness modifiers|kb:Property modifiers] would need to be derived for the entire section.


h2. What causes jumps in the moment diagram of a composite-section frame?

*Answer:* The deck and girders of a composite section are connected through common [joints|kb:Joint]. During composite action, forces are transferred from the deck to the girders through these joints. These forces, concentrated at the connection points, cause jumps in the moment diagram. Discontinuities may be reduced by refining the [discretization|kb:Discretization] of [frame|kb:Frame] and [shell|kb:Shell] elements such that girder and deck connection points have closer spacing.


h2. Is there any difference between the modeling of composite sections in SAP2000 and ETABS?

*Answer:* Composite-section modeling and analysis is similar between [SAP2000|sap2000:home] and [ETABS|etabs:Home]. One additional capability of ETABS is that the software can design the elements of a composite section.


h2. How are design forces obtained for a composite section modeled using frame and shell elements?

*Extended question:* I modeled a composite [reinforced-concrete|kb:Concrete] T-beam floor system using [finite elements|kb:Meshing] for the slab and [frame|kb:Frame] elements for the girders. I found that member forces cannot be directly read for the design process. How are member forces obtained for design?

*Answer:* Design of a T-beam floor system is dependent upon the forces on both the girder and the tributary slab width. Design forces are derived as a combination of those within the frame and [shell|kb:Shell] elements which compose the composite system.

Design forces may be obtained using either of the following methods:

* Users may create a sequence of [section cuts|kb:Section cut FAQ#Can the program display force diagrams based on a sequence of section cuts?], as described on the Section cut FAQ page, to obtain design forces. Done manually, this process may require significant effort. A more practical approach may be to automate the process using the [Application Programming Interface|API] (API). Please note that discretization should be refined as necessary to adequately define the section cuts.

* Users may also obtain design forces by replacing rectangular beams with T-Beam sections, then using [property modifiers|kb:Property modifiers] to modify adjacent shell elements such that they do not contribute the same stiffness and weight as the T-beams. Frame forces in the T-Beams would then directly correspond to the composite-section design forces.


h2. How is non-composite action modeled for frame-element girders and shell-element slabs?

*Answer:* When common [joints|kb:Joint] connect a girder and a slab, composite action occurs. Users may offset the slab from the girder using joint offsets and frame [insertion points|kb:Insertion point], described further in the [Composite section|tutorials:Composite section] tutorial. Composite action may also result when girders and slabs do not share common joints, but instead are connected through full-body constraints, which connect girder joints to certain corresponding slab joints.

Non-composite action results when the girder and slab both individually contribute to stiffness properties. Slip is allowed along the slab-girder interface. To model non-composite action, the girder and slab should not share common joints, but they should be connected such that corresponding joints share the same vertical deflection. For example, a horizontal girder connected to a non-composite slab may be modeled using the _equal Z constraint_.

A condition where the slab does not contribute to stiffness may be modeled using [property modifiers|kb:Property modifiers] where flexural and axial stiffness are reduced in the direction parallel to girders. Very small values on the order of 1e-3 are recommended to avoid the numerical problems which may result from zero-modifier application. To model the stiffness contribution from forms, property modifiers may also be applied in the direction perpendicular to girders.