bridgelink-user-guide
bridgelink-user-guide
March 2020
Table of Contents
3.1 Terminology
PGSuper conducts a time-step analysis that follows a typical construction sequence for
precast-prestressed girder bridges. The typical construction sequence comprises five
construction events (referred to as Stages in previous versions of PGSuper). Each
construction event is further divided into one or more analysis intervals. Refer to Table 1
for a summary of the construction events and analysis intervals in PGSuper.
Edit → Alignment or click the “Edit Roadway Alignment and Profile” icon, .
Roadway Cross Sections – Define the cross slopes and cross slope transitions under
this tab.
3.3 Bridge Geometry, Beam Type, Beam Spacing, and Beam working
point
General – The default location for Bridge Line in PGSuper is at the center of the
beams. The default value for Alignment is along the Bridge Line (Bridge Line Offset =
0). The Locate field allows the user to specify modified girder locations relative to the
Bridge Line or the Alignment. The Location of Girder Working Points field allows the
user to select from what point the beam or girder will be rotated when the field Girder
Orientation is set to any of the Normal to Roadway options.
then the Girder Type and Spacing may be modified through Edit → Span... by
choosing a span and selecting the Girders tab. Note that girder spacing can also be
accessed through Edit → Abutment\Pier... under the Girder Spacing tab.
Layout – Define span length(s), and specify the location and orientation of all
abutments interior piers.
The user may also access Abutment, Span, or Pier options by clicking the appropriate
Edit button under the Piers\Spans heading. This provides quick access for modifying
various details including span length, beam connection type, girder type, and girder
spacing. Note, however, that girder type and spacing can only be modified if the bridge’s
general settings meet one of the three aforementioned conditions.
Check the Sidewalk option to add a sidewalk to one or both sides of the roadway. The
user may edit sidewalk dimensions and material properties. Additionally, the user can
specify an Interior Barrier to separate the sidewalk from the roadway. The user is
referred to Section 3.6.2 for a discussion of modeling sidewalk live loads in PGSuper.
Deck Geometry and Materials – Use this tab to specify dimensions and material
properties for the concrete slab and/or overlay.
A note on modeling overlays: In the past, TxDOT designed bridge components for the
gravity load of a future 2” overlay. This practice was occasionally waived to limit release
strengths of pretensioned beams and girders. The practice was discontinued all-together
in 2012. Presently, the user should only specify an overlay when it is called for in the
current design.
Gross Depth defaults to the concrete slab thickness specified in the TxDOT LRFD
Bridge Design Manual for the chosen beam type. For example, pretensioned concrete I-
girders, gross depth is equal to the standard slab thickness of 8.5 inches. For
pretensioned concrete box girders, on the other hand, the minimum slab thickness is 5.0
inches.
Slab Offset is the slab thickness plus haunch thickness. The user is referred to Section 4
for a discussion of how haunch can be modeled in PGSuper.
Deck Reinforcement – Disregard this tab. Deck reinforcement does not affect
computations in PGSuper.
As discussed previously, a preliminary beam design may be conducted using the Girder
Designer. Access the Girder Designer via Project → Design Girder... or click on the
“Design Girder” icon, .
Girders may also be designed or modified manually. Access the manual design tool via
Edit → Girder or click the “Edit girder” icon, . Then, select a girder to edit.
General – Specify concrete properties, including the release strength (f ′ci) and
compressive strength (f ′c).
What are your options when your release strength exceeds the limit? Use a deeper
beam section (e.g., use Tx46 beams instead of Tx40 beams).
What if the vertical clearance prohibits the use of a deeper beam section? Reduce
the span length.
What if the span length can’t be reduced? Reduce Beam Spacing. If the beam
spacing is less than 6 feet, we recommend reducing the overhang width to S/2 or less. As
a general guideline, the overhang should not be less than 2 feet.
What if my beam spacing is less than 4 feet and my release strength is still high?
Use a non-standard strand pattern. The Edit → Girder... feature in PGSuper allows you
to manually change the strand pattern to reach a lower release strength. This procedure is
shown in Appendix B.
In the Project menu of the main toolbar, the following items have been set to default
TxDOT values:
*YEAR* indicates the latest AASHTO LRFD Bridge Design Specification (or interim
updates) that TxDOT has adopted. For example: TxDOT 2015 refers to the AASHTO
LRFD Bridge Design Specification, Seventh Edition, 2014 with 2015 interim revisions
and modifications for TxDOT policy as outlined in the TxDOT LRFD Bridge Design
Manual.
The user can bypass TxDOT modifications by changing this selection to LRFD *YEAR*.
TxDOT 2010 and later project criteria default to a release factor of 0.65 per the
memorandum titled “Design Release Strengths for Prestressed Concrete Beams,” dated
August 26, 2010.
3.6 Loads
3.6.1 User Defined Loads
The user can model additional loads (e.g., light poles, medians, or signs) with user
defined loads.
When defining a load, the available load cases are DC (dead load, component), DW
(dead load, wearing surface), and LL+IM (live load plus impact). DC and DW load cases
may be applied during Event 4 or Event 5. The LL+IM load case can only be applied
during Event 6.
Discrete objects such as light poles or signs should be modeled using the “Add New
Point Load” feature. The user would choose the DC load case for these objects and apply
the loads during Event 5.
PGSuper assumes the rail and sidewalk are located at the edge of the slab and models this
scenario by distributing the rail, sidewalk, and pedestrian live loads equally among the
exterior 3 beams. However, when modeling U beams, 2/3 of the rail weight is applied to
the exterior beam and 1/3 to the first interior beam. If you want to distribute the load
differently, you can set the rail to “none” and instead add the rail load in “User Defined
Loads” with the “Add Distributed Load” feature.
The program allows you to select which truck you would like to use for Service and
Strength Limit States, Fatigue Limit State, and Permit Limit States. Default settings are
HL-93, the Fatigue truck, and no truck, respectively.
If you model a sidewalk, PGSuper will automatically turn on the Pedestrian on Sidewalk
load. By default, PGSuper will envelope the sidewalk live load and the vehicular live
load. The pedestrian live load can be turned off by unchecking the box beside the load
case.
PGSuper distributes the pedestrian live load over the three exterior beams, as specified in
the TxDOT LRFD Bridge Design Manual.
The following three steps may be used to model the sidewalk and pedestrian loads
differently than the PGSuper default:
1. Do not define a sidewalk. The program will apply the vehicular load to all the
beams.
2. Add a User Defined Distributed Load to distribute the sidewalk dead load. (DC,
Bridge Site Stage 2).
3. Add a User Defined Distributed Load to distribute pedestrian live load (LL+IM,
Bridge Site Stage 3).
The program defaults to calculating the live load distribution factors using the AASHTO
LRFD Bridge Design Specification with modifications for TxDOT policy as outlined in
the LRFD Bridge Design Manual.
Occasionally, a bridge will fall outside the Ranges of Applicability (ROA) of the various
methods in the ASSHTO Specifications. In such cases, the Preliminary Girder Designer
in PGSuper will warn the user:
Live Load Distribution Factors could not be calculated for the following reason
xxxxx. See Table 4.6.2.2.2b-1. A refined method of analysis is required for this
bridge. See Status Center for Details.
The status center can be accesses by clicking on the red “X” or the yellow “!”. Open the
Refined Analysis Options dialogue shown in Figure 1 by clicking on the error message in
the status center.
The Ranges of Applicability (ROA), found in Section 4.6.2.2 of the AASHTO LRFD
Bridge Design Specifications, reflect the limits of the research that was conducted to
investigate distribution factors. The ROA do not necessarily indicate the range for which
the formulas are valid; rather, they reflect the limits of what was studied in the
development of the formulas.
When a design falls outside the ROA, it is left up to the engineer's judgment to decide
whether to apply the formulas or determine the live load distribution factor by some other
method. To aide this decision, an engineer might first determine the sensitivity of the
formula in question to the variable in question. Such a study would be conducted over a
range that comprises the ROA and the design value(s).
How do you decide which option you should select? This issue comes down to
engineering judgment and experience. Some guidelines are as follows:
• If all the parameters are within the ROA, use the value as calculated by PGSuper.
• If the ROA are violated by a great amount, use the lever rule. An example of this
would be S = 20 feet, when the range is 3.5 to 16 feet.
Live Load Distribution factors can be modified at any time through Loads Live Load
Distribution Factors. The dialogue that appears offers the same options as shown above.
3.) Click the Edit button for the appropriate Pier # in the Piers\Spans column:
5.) Increase the Bearing Offset and End Distance values by an amount equal to
half of the Inverted T stem width. Bearing Offset is the distance from the
centerline of the bent to the centerline of the bearing. End Distance is the
distance from the centerline of the bearing to the end of the girder. The
difference in these two numbers is the value typically shown on our plans
(e.g., 3"). The diagram on the right side illustrates these values and how they
are measured.
6.) End Distance and Bearing Offset are always measured Normal to
Abutment/Pier Line for an Inverted T. Select this option in both drop-down
menus:
Bearing Offset:
End Distance:
The Bearing Seat information can be found in the Geometry Report of the Bridge.
4 Haunch
PGSuper is capable of computing haunch geometry and applying haunch loads.
TxDOT users have traditionally accounted for haunch with a user-defined distributed
load that approximates the actual haunch load. Users who wish to continue using this
“manual” approach may do so, but must first disable haunch in PGSuper.
Conversely, the user may utilize PGSuper to compute and apply the haunch load. This
approach is recommended for any girder design, especially when the superstructure
geometry is complicated. The haunch algorithm accounts for all aspects of roadway and
girder geometry. Users who wish to use this “automated” approach must enable haunch
in PGSuper.
The haunch algorithm, when enabled, computes the space between the bottom of a bridge
deck and the top of a girder. Horizontal curvature, vertical curvature, crown points, and
superelevation are based on user inputs in the Edit → Alignment dialog. Deck thickness,
span lengths, and skew are based on user inputs in the Edit → Bridge dialog. If haunch
is enabled, the top of the beam is modeled as a parabola defined by the control points
shown in Figure 2.
Haunch geometry relies on three variables: fillet, slab offset, and excess camber. Users
can edit these values in Edit → Haunch. They are defined as follows:
fillet – minimum haunch depth. This serves as a buffer that prevents the girder from
intruding into the deck. In most cases, haunch depth is equal to fillet depth at mid-span,
on the least-haunch edge of the girder. The appropriate value (i.e., the required buffer)
depends on which type of prestressed concrete girder is being used:
slab offset – distance from top of girder to top of deck at the intersections of girder
centerline and bearing centerline; usually called out as “X” dimension on TxDOT plan
sheets. Users may define a single value for the entire bridge, one value for each bent, or
a unique value for each point of bearing.
5 TOGA
TxDOT has developed an Optional Girder Analysis plug-in for PGSuper. This plug-in,
called TxDOT Optional Girder Analysis (TOGA), may be accessed as follows:
File → New
Then choose a girder type as shown in Figure 3, select a template, and click OK. For
additional instructions in using TOGA, open a TOGA template and select Help → Help
Topics. The Help Topics comprise a very comprehensive guide to TOGA.
Appendix A
Example Girder Design with Known Haunch
2. Define
Number of
Beams 1. Define
Working
point
3. Define
Girder
Spacing
4. Define
Girder
Orientation
The Working point for TxGirders and I-Beams should be set to Top Centerline of
Girders and the Girder Orientation should be set to Plumb. The Working point for Box
Beams, X-Beams, U Girders, Slab Beams, and Decked Slab beams should be set to
Bottom Centerline of Girders and the Girder Orientation should be set to one of the
Normal to Roadway options.
If haunch is disabled, delete any vertical curves from the Profile tab. Otherwise, the
program will add haunch load without adjusting for camber or dead load deflection.
If haunch is disabled, ensure that all segment slope entries are set equal to zero. Otherwise, the
program will add haunch load without adjusting for camber or dead load deflection.
Check this box to accept the current haunch design parameters (i.e., Slab Offset and
Assumed Excess Camber). The user can apply these parameters to the current girder only,
to all girders in the span, or to all girders in the bridge (as shown).
1. Click OK
Select a location to
save the file
2. Provide a name
for the Export file
1. Click Save
Appendix B
Method for Developing a Non-Standard Strand Pattern
with the Haunch Algorithm Enabled
4. Select a location to
save the Excel file
1. Click OK
2. Name the file
2. Select Bridge
Geometry Report
The Contents of the
report will have all data
selected, scroll down to
locate the Bearing Seat
Elevations information.
The following section in
the report will display the
Bearing Seat Elevations
at Girder Bottom Edges
these are the ones used
when using Box Beams,
1. Select the data to X-Beams, U-Beams, Slab
be included in the Beams, or Decked Slab
report.
Appendix C
Procedure to Disable Haunch Algorithm
If haunch is disabled, do NOT model vertical curvature or cross slope. In the alignment dialog, delete any vertical
curves from the Profile tab and ensure that the segment slope entries on the Roadway Cross Sections tab are equal to
zero. Otherwise, the program will add haunch load without adjusting for camber or dead load deflection.