Simon LRFD

LRFD Simon
User's Guide
version: 10.3 (AASHTO 8th Edition)
June 2018
www.steelbridges.org
Copyright © 2018, AISC. All Rights Reserved. Except as otherwise
permitted by the American Institute of Steel Construction (AISC), this
publication, or parts thereof, may not be reproduced in any form, by any
method, for any purpose.
Certain materials included in this publication are reprinted with the

permission of the copyright holder.
Disclaimer
THIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AISC
"AS IS." AISC DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE REGARDING THESE MATERIALS.
1 INTRODUCTION ......................................................................................................................................... 6
2 GETTING STARTED ....................................................................................................................................10

2.1 GENERAL .......................................................................................................................................................10
2.2 MENU OPTIONS..............................................................................................................................................10
2.2.1 Help Menu..............................................................................................................................................10
2.2.2 File Menu ...............................................................................................................................................12
2.2.2.1 New Model.................................................................................................................................................... 12
2.2.2.2 Open Model .................................................................................................................................................. 13
2.2.2.2.1 Sample Input Files .................................................................................................................................... 15
2.2.2.3 Save Model ................................................................................................................................................... 18
2.2.2.4 Save Model As ............................................................................................................................................... 18
2.2.2.5 Save Input Verification .................................................................................................................................. 18
2.2.2.6 Model Properties .......................................................................................................................................... 18
2.2.2.7 Close Model ........................................................................................................................................................ 19
2.2.2.8 Print Results ....................................................................................................................................................... 19
2.2.2.9 Exit ................................................................................................................................................................ 19
2.2.3 Analyze Menu ........................................................................................................................................20
2.3 TOOL STRIP BUTTONS ......................................................................................................................................23
3 INPUT FORMS ...........................................................................................................................................25
3.1 GENERAL .......................................................................................................................................................25

3.2 GENERAL PROPERTIES FORM .............................................................................................................................27
3.2.1 General ..................................................................................................................................................27
3.2.2 General Properties Form Data ...............................................................................................................28
3.3 DISTRIBUTION FACTORS FORM ..........................................................................................................................30
3.3.1 General ..................................................................................................................................................30
3.3.2 Distribution Factors Form Data..............................................................................................................34
3.4 MATERIAL PROPERTIES FORM............................................................................................................................36
3.4.1 General ..................................................................................................................................................36
3.4.2 Material Properties Form Data ..............................................................................................................37
3.5 LOADS FORM .................................................................................................................................................39
3.5.1 General ..................................................................................................................................................39
3.5.2 Long-Term Composite Dead Loads ........................................................................................................39
3.5.3 Live Load Information ............................................................................................................................39
3.5.4 Loads Form Data ....................................................................................................................................41
3.6 USER DEFINED DESIGN VEHICLE PROPERTIES FORM ...............................................................................................42
3.6.1 General ..................................................................................................................................................42
3.6.2 User Defined Design Vehicle Form Data ................................................................................................44
3.7 TRANSVERSE STIFFENER PROPERTIES FORM ..........................................................................................................46
3.7.1 General ..................................................................................................................................................46
3.7.2 Transverse Stiffener Properties Form Data ............................................................................................48
3.8 SHEAR STUD PROPERTIES FORM.........................................................................................................................49
3.8.1 General ..................................................................................................................................................49
3.8.2 Shear Stud Properties Form Data...........................................................................................................50
1
3.9 BOX GIRDER PROPERTIES FORM .........................................................................................................................52
3.9.1 General ..................................................................................................................................................52
3.9.2 Box Girder Properties Form Data ...........................................................................................................53
3.10 SPAN INFORMATION FORMS..............................................................................................................................56
3.10.1 General ..............................................................................................................................................56
3.10.2 Symmetrical Span Declaration ..........................................................................................................56
3.10.3 Non-Composite Uniform Dead Load ..................................................................................................57
3.10.4 Hinges ................................................................................................................................................58
3.10.5 Non-Composite Partial Uniform Dead Load ......................................................................................58
3.10.6 Bottom Flange Cross-Frame Spacing .................................................................................................59
3.10.7 Top Flange Cross-Frame Spacing .......................................................................................................60
3.10.8 Span Information Form Data .............................................................................................................61
3.11 CROSS SECTION INFORMATION FORMS ................................................................................................................66
3.11.1 General ..............................................................................................................................................66
3.11.2 Web Cross Section Information Form ................................................................................................67
3.11.2.1 General.......................................................................................................................................................... 67
3.11.2.2 Web Depth, Thickness &Yield Stress ............................................................................................................. 68
3.11.2.3 Web Stiffener Parameters ............................................................................................................................ 69
3.11.2.3.1 Transversely Stiffened Check Box ........................................................................................................... 69
3.11.2.3.2 Minimum Transverse Stiffener Spacing .................................................................................................. 70
3.11.2.3.2.1 LRFD Analysis Run Option ............................................................................................................... 70
3.11.2.3.2.2 LRFD Design Run Option ................................................................................................................. 70
3.11.2.4 Web Cross Section Information Form Data................................................................................................... 72
3.11.3 Top Flange Cross Section Information Form ......................................................................................74
3.11.3.1 General.......................................................................................................................................................... 74
3.11.3.2 Top Flange Cross Section Information Form Data ......................................................................................... 76
3.11.4 Bottom Flange Cross Section Information Form ................................................................................78
3.11.4.1 General.......................................................................................................................................................... 78
3.11.4.2 Bottom Flange Cross Section Information Form Data................................................................................... 79
3.11.5 Slab Cross Section Information Form .................................................................................................81
3.11.5.1 General.......................................................................................................................................................... 81
3.11.5.2 Slab Cross Section Information Form Data ................................................................................................... 82
3.11.6 Field Splice Cross Section Information Form ......................................................................................83
3.11.6.1 General.......................................................................................................................................................... 83
3.11.6.2 Field Splice Cross Section Information Form Data ........................................................................................ 86
3.11.7 Deck Pour Cross Section Information Form .......................................................................................87
3.11.7.1 General.......................................................................................................................................................... 87
3.11.7.2 Deck Pour Cross Section Information Form Data .......................................................................................... 89
3.12 COST FORMS ..................................................................................................................................................90
3.12.1 General ..............................................................................................................................................90
3.12.2 Material Unit Cost Form ....................................................................................................................90
3.12.2.1 General.......................................................................................................................................................... 90
3.12.2.2 Material Unit Cost Form Data ....................................................................................................................... 92
3.12.3 Fabrication Cost Factor Form ............................................................................................................92
3.12.3.1 General.......................................................................................................................................................... 92
3.12.3.2 Fabrication Cost Factor Form Data ............................................................................................................... 94
2
3.13 WEB DEPTH OPTIMIZATION ..............................................................................................................................95
3.13.1 General ..............................................................................................................................................95
3.13.2 Web Depth Optimization Form Data .................................................................................................97
3.14 RESULT CONTROLS ..........................................................................................................................................99
3.14.1 General ..............................................................................................................................................99
3.14.2 Result Controls Form Data ...............................................................................................................100
4 RESULTS ................................................................................................................................................. 101
4.1 GENERAL .....................................................................................................................................................101
4.2 RE-STYLIZED OUTPUT ....................................................................................................................................102
4.3 USER MANIPULATION OF RESULTS....................................................................................................................102
4.4 CREATION OF A NEW MODEL INPUT FILE FROM THE BEST DESIGN ..........................................................................105
5 PROGRAM ANALYSIS & DESIGN METHODOLOGY ..................................................................................... 107
5.1 GENERAL .....................................................................................................................................................107
5.1.1 LRFD Analysis Run Option ....................................................................................................................107
5.1.2 LRFD Design Run Option ......................................................................................................................107
5.2 ANALYSIS .....................................................................................................................................................107
5.3 DESIGN .......................................................................................................................................................110
5.3.1 General ................................................................................................................................................110
5.3.2 Calculation of Factored Loads/Stresses ...............................................................................................110
5.3.2.1 Strength Limit State .................................................................................................................................... 110
5.3.2.2 Service Limit State ....................................................................................................................................... 111
5.3.2.3 Fatigue Limit State ...................................................................................................................................... 112
5.3.3 Performance Ratio & Location of Section Checks ................................................................................113
5.3.4 Redesign...............................................................................................................................................115
5.3.4.1 General........................................................................................................................................................ 115
5.3.4.2 Box Girders.................................................................................................................................................. 121
5.3.5 Web Depth Optimization .....................................................................................................................124
5.3.6 Bill of Materials ....................................................................................................................................128
5.3.6.1 General........................................................................................................................................................ 128
5.3.6.2 Transverse Stiffener Design ........................................................................................................................ 129
5.3.6.2.1 Transverse Stiffener Spacing .................................................................................................................. 129
5.3.6.2.2 Transverse Stiffener Sizing ..................................................................................................................... 130
5.3.6.3 Bearing Stiffener Design.............................................................................................................................. 130
5.3.6.4 Longitudinal Web Stiffeners ........................................................................................................................ 131
5.3.7 Shear-Connector Design.......................................................................................................................133
5.3.8 Field Splice Design Information (for NSBA Splice) ................................................................................135
5.3.9 Fatigue Design .....................................................................................................................................135
5.3.9.1 General........................................................................................................................................................ 135
5.3.9.2 Details Checked and Redesigned ................................................................................................................ 136
5.3.9.3 Details Checked and Not Redesigned but Warning Printed ........................................................................ 137
5.3.9.4 Details Not Checked .................................................................................................................................... 138
5.3.10 Lateral-Torsional Buckling ...............................................................................................................139
5.3.11 Hinged Bridges.................................................................................................................................141
5.3.12 Reactions .........................................................................................................................................141
3
6 PROGRAM LIMITATIONS ......................................................................................................................... 143
APPENDIX A: QUICK INSTALLATION GUIDE ...................................................................................................... 145

BEFORE YOU BEGIN ....................................................................................................................................................146
SOFTWARE PREREQUISITES ...........................................................................................................................................146
INSTALLING LRFD SIMON ............................................................................................................................................147
WINDOWS START MENU AND APPLICATION SHORTCUT .....................................................................................................150
SAMPLE INPUT FILES ...................................................................................................................................................151
QUESTIONS AND DEFECT REPORTING .............................................................................................................................151
APPENDIX B – REVISION HISTORY.................................................................................................................... 152

SUMMARY OF MAY 2018 REVISIONS - VERSION 10.3.0.0 (AASHTO 8TH EDITION) ...............................................................153
Input Revisions ............................................................................................................................................................... 153
Output Revisions ............................................................................................................................................................ 153
Installation Related Revisions......................................................................................................................................... 153
SUMMARY OF OCTOBER 2017 REVISIONS - VERSION 10.2.1.0 ..........................................................................................154
Input Revisions ............................................................................................................................................................... 154
Specification Related Revisions ...................................................................................................................................... 154
SUMMARY OF MARCH 2015 REVISIONS - VERSION 10.2.0.0.............................................................................................155
User's Guide Revisions ................................................................................................................................................... 155
GUI Revisions.................................................................................................................................................................. 155
SUMMARY OF FEBRUARY 2015 REVISIONS - VERSION 10.1.1.14 .......................................................................................156
SUMMARY OF FEBRUARY 2015 REVISIONS - VERSION 10.1.1.13 .......................................................................................157
Program Input Revisions ................................................................................................................................................ 157
Programming Revisions .................................................................................................................................................. 158
SUMMARY OF SEPTEMBER 2014 REVISIONS - VERSION 10.1.1.12 .....................................................................................159
User Interface Revisions ................................................................................................................................................. 159
SUMMARY OF AUGUST 2014 REVISIONS - VERSION 10.1.1.11 (AASHTO 7TH EDITION) ........................................................160
SUMMARY OF JULY 2014 REVISIONS - VERSION 10.1.1.10 ...............................................................................................162
SUMMARY OF OCTOBER 2013 REVISIONS - VERSION 10.1.1.9 ..........................................................................................163
SUMMARY OF MARCH 2013 REVISIONS - VERSION 10.1.1.8.............................................................................................164
4
SUMMARY OF REVISIONS - VERSION 10.1.1.7 .................................................................................................................165
SUMMARY OF REVISIONS - VERSION 0.0.1.0 ...................................................................................................................174
5
1 INTRODUCTION
LRFD Simon is a complimentary software program offered by the National Steel Bridge Alliance
(NSBA) for preliminary steel plate and box girder design. LRFD Simon is one of the primary
design resources offered by the NSBA as part of an overall industry service to encourage the
use of structural steel for bridges. For more information on the other design resources offered
by the NSBA, please visit the NSBA homepage at www.steelbridges.org. A Quick Installation
Guide for LRFD Simon is provided in Appendix A.
LRFD Simon is a powerful line-girder analysis and design program that allows the user to quickly
produce complete steel superstructure designs in accordance with the 8th Edition AASHTO LRFD
Bridge Design Specifications. The program is intended for the preliminary design of steel I-
shaped plate girders and multiple single-cell box girders. Each girder may be a simple span, or it
may consist of up to 12 continuous spans.
The Simon program, named after singer/songwriter Paul Simon who wrote the classic single
“Bridge over Troubled Water” in the late 1960s, was originally developed by the U.S. Steel
Corporation in cooperation with the Wisconsin Department of Transportation in the mid-to-late
1970s. The program was widely used by State DOTs and consultants for about two decades,
primarily on a mainframe platform, to produce designs in accordance with the AASHTO
Standard Specifications for Highway Bridges. The program was then converted to run on
personal computers by the American Institute of Steel Construction (AISC) in the mid-1990s,
but gradually fell out of favor with the advent of the new millennium as more and more State
DOTs moved toward adoption of the new AASHTO LRFD specifications. The NSBA was able to
successfully re-launch the Simon program in 2012 with an updated analysis engine, support for
the AASHTO LRFD specifications, and a completely new user-friendly interface to allow the user
to quickly and conveniently enter the required input and view the program results.
The original strategy used to develop the Simon program was to basically design a bridge the
same way a bridge engineer would manually design a bridge, thus making the program more
user-friendly to designers. Experience over nearly four decades of use has indicated that this
strategy is sound. The program is strongly dependent on the input data defining the starting
design and control parameters selected by the user. A basic assumption is made that the user
is familiar with bridge design and can select suitable starting designs, along with the necessary
design parameters that are unaltered by the program; notably, flange widths, splice locations,
girder depths and steel yield strengths.
To use LRFD Simon, the bridge designer inputs a trial girder design, which may only be a rough
approximation of the final design and need not satisfy specification requirements. LFRD Simon
will automatically perform a validation of the input data prior to running the analysis.
Whenever an existing model is opened, a report of the latest consistency checks on the input
data for the model will appear immediately. The report can be printed by the user, if desired.
6 INTRODUCTION
A validation of the input data can also be requested by the user at any time. A line-girder
analysis is then performed. The user can choose to have the program either evaluate the input
trial design for one design cycle, or have the program proportion the principal girder elements
in accordance with the AASHTO LRFD specifications using the input trial design as a starting
point; that is, LRFD Simon will execute the analysis and design of the girder elements
automatically until an improved final design is found. If the current design violates the AASHTO
provisions, the design is modified by LRFD Simon to correct the violations; otherwise, the
design is made lighter, if possible. Throughout the execution of LRFD Simon, the user has the
option to display the information generated during each design cycle so that the user can later
trace the design process. At the end of a successful final design cycle, transverse and bearing
stiffeners plus stud shear connectors are designed and a bill of materials is produced. LRFD
Simon also automatically generates a new model input file from the best design; that is, an
input file with the revised web and flange plate sizes from the successful final design cycle for
possible subsequent investigations.
It is important to keep in mind that a successful final design produced by LRFD Simon does not
necessarily mean the attainment of a “best” design; the attainment of a “best” design is still left
to the judgment of the design engineer. Basically, LRFD Simon quickly and accurately handles
all of the structural engineering calculations required for the superstructure design, thereby
permitting an engineer to conveniently investigate numerous alternative designs. For example,
LRFD Simon can assist the user with the optimization of the vertical web depth of a steel I- or
box girder by allowing the user to quickly generate a series of designs at different web depths in
order to arrive at an optimum cost-effective depth based on weight and/or cost.
LRFD Simon is applicable to non-composite or composite (steel-concrete), doubly symmetric or

singly symmetric, and homogeneous or hybrid cross-sections. The program can be used for
constant web-depth members or variable web depth members with parabolic or linear
haunches. Transversely stiffened webs, with or without longitudinal stiffeners, or unstiffened
webs are permissible. Partially stiffened webs, where a minimum number of transverse
stiffeners are located only near the supports, are attainable by holding the web to a specified
minimum thickness during the design iterations. For box girders, LRFD Simon will select the
optimum size of bottom-flange longitudinal tee stiffeners, as necessary based on relative cost
data supplied by the user. Numerous fatigue checks are also made by LRFD Simon.
The Simon program was originally developed for the design of tangent I- and box-girder bridges
with limited or no skew, and the program results are most applicable and accurate for those
types of bridges. With experience and by making some rational and proper assumptions, the
program can also potentially be used to prepare reasonable approximate preliminary starting
trial girder designs for horizontally curved bridges and straight bridges with more significant
skew for input into more refined analysis programs. It is not recommended that the LRFD
Simon results be used for the final design of those types of bridges.
INTRODUCTION 7
Output from LRFD Simon includes (but is not limited) to the following:
 A listing of the input data for user verification;

 Dead-load moments and shears for girder self-weight, other non-composite (DC1) dead
loads, composite (DC2) dead loads, utilities and wearing surface (DW) loads at span
tenth points;
 Maximum and minimum live-load moment and shear envelopes for AASHTO HL-93
loading, an optional user-defined vehicle with up to 40 axles and the AASHTO fatigue
load at span tenth points;
 Dead- and live-load vertical support reactions;
 Dead-load deflections at span tenth points and maximum live-load deflections in each
span;
 Performance ratios computed for each design limit state at critical cross-sections of the
girder along with the specific AASHTO LRFD article for which a particular element in the
cross-section was examined;
 Factored stresses and section property information at each critical cross-section
examined, including stresses for an optional construction lateral moment and sequential
deck pouring sequence defined by the user;
 The required minimum size and suggested spacing of any transverse web stiffeners;
required minimum sizes of bearing stiffeners; and optionally, size and suggested pitch
information for stud shear connectors;
 A complete bill of materials including locations, yield strengths, weights, lengths, widths
and thicknesses of all webs, flanges and stiffeners. Estimated cost information is also
provided whenever the user enters the current prevailing costs of various steel grades
and other estimated fabrication cost factors.
The intent of this User’s Guide is to familiarize the user with the numerous capabilities of LRFD
Simon to allow the user to use the program more efficiently in order to prepare more cost-
effective preliminary steel girder designs. Included within this User’s Guide is the following:
 Descriptions of the various menu options and tool strip buttons provided as part of the
new user interface to help the user get started with LRFD Simon;
 Descriptions of the various LRFD Simon input forms and the input data that are to be
provided on each of these forms;
 Descriptions of the LRFD Simon output (results) and the creation of a new model input
file from the best design arrived at by LRFD Simon (Article 4.4);
 Descriptions of the Program Analysis and Design Methodology;
 Descriptions of the Program Limitations, including a list of items that are currently not
covered or considered in LRFD Simon;
 Descriptions and summary of the revision history of LRFD Simon (Appendix B).
8 INTRODUCTION
The user is strongly encouraged to study and become familiar with the material presented in
this User’s Guide in order to better understand how the program works, the inherent design
assumptions that are made internally within the program, and the current capabilities and
limitations of the program. This should allow the user to use the program more effectively and
efficiently in order to produce better quality preliminary steel-girder designs that satisfy the
majority of the AASHTO LRFD specifications.
INTRODUCTION 9
2 GETTING STARTED
2.1 General
After LRFD Simon is successfully installed, double-click on the LRFD Simon desktop icon to run
the program. Upon execution of LRFD Simon, a window will appear on the screen containing a
blank form, a Menu Bar containing three Menu Options, and a series of Tool Strip Buttons
(Exhibit 1).
Menu Bar
Tool Strip Buttons
Exhibit 1: Initial Blank Form upon Execution of LRFD Simon.
Each of the Menu Options on the Menu Bar to help the user get started is described below,
followed by a description of the functions of the various Tool Strip Buttons.
2.2 Menu Options

2.2.1 Help Menu
The Help Menu Option may be used at any time to bring up a searchable .PDF of this LRFD
Simon User’s Guide, which also may be printed (Exhibit 2). The User’s Guide can also be
10 GETTING STARTED
opened up at any time by pressing “F1” on the keyboard when in any input field (except for the
input fields on the Cross Section Information Form).
Exhibit 2: Help Menu Option: LRFD Simon User's Guide.
The Help Menu Option can also be used to open up a pop-up window showing the current
version number and month of issue of the software, the program disclaimer, instructions on
where to go to obtain further information on the software, and where to send any comments
and questions on the software (Exhibit 3). This window is opened by clicking on About LRFD
Simon in the Help menu (Exhibit 3). After viewing this information, right click inside the pop-
up window to close the window.
Exhibit 3: Help Menu Option: 'About LRFD Simon' Pop-Up Window.
GETTING STARTED 11
2.2.2 File Menu
The File Menu Option may be used to create a new LRFD Simon model, open an existing LRFD
Simon model, print the LRFD Simon results, or exit the program, as described further below.
2.2.2.1 New Model
Click on File and then on New Model to create a new LRFD Simon model (alternatively, hold
down the ‘CTRL’ key and enter ‘N’). A New Model window will open up allowing the user to
enter a Job Name, Project Name and Description (Exhibit 4).
Exhibit 4: File Menu Option: New Model Window.
Click on ‘OK’ to save the entered data, exit the New Model window and begin entering the
model data on the blank LRFD Simon input forms, as described in the next section of this User’s
Guide. In the title bar of the blank forms, <New Model > indicates that the user has not saved
the model and given it a name yet, while the asterisk (*) after <New Model> indicates that
there are unsaved changes to the model.
12 GETTING STARTED
User Note: The Library File option shown in the New Model Window in
Exhibit 4 is reserved for future use. The default Library File is currently
named NSBA.
2.2.2.2 Open Model
As shown in Exhibit 5, click on File and then on Open Model to open an existing LRFD Simon
model (alternatively, hold down the ‘CTRL’ key and enter ‘O’). An Open Model window will
open up allowing the user to browse for and open an existing LRFD Simon model (Exhibit 6).
Note that the extension on all LRFD Simon model input files is .dat.
Exhibit 5: File Menu Option: Open File.
GETTING STARTED 13
Exhibit 6: Open Model Window.
Alternatively, when clicking on File, the path for up to five of the most recently selected LRFD
Simon model input files will be displayed. Selecting any one of these paths will automatically
open up the LRFD Simon model input file associated with that path (Exhibit 7).
14 GETTING STARTED
Exhibit 7: File Menu Option: Opening an Existing Model using a Recent File Path.
2.2.2.2.1 Sample Input Files
Several sample I- and box-girder input files are provided as part of the LRFD Simon installation
in the default folder name ‘LRFD Simon (AASHTO 8th Edition) Models’ underneath the user’s
Windows Documents folder (unless a different name and/or location for this folder was
specified by the user during the program installation – see Appendix A). The sample input files
are contained in sub-folders underneath the main folder. Basic descriptions of these input files
are provided below in Exhibit 8a: Description of LRFD Simon Sample Input Files. and Exhibit 9a:
Description of LRFD Simon Sample Input Files (con’t).:
GETTING STARTED 15
Exhibit 8a: Description of LRFD Simon Sample Input Files.
File Name Sub-Folder Girder Type Number of Spans Span Arrangement Additional Notes
BG11.DAT 270' Two Box Girders
…\1 Span\Box Girder\ Box Girder
BG12.DAT 151'
IG11.DAT 158'
IG12.DAT 204'
1
IG13.DAT 270'
…\1 Span\Plate Girder\ Plate Girder
IG14.DAT 184'
IG15.DAT 140'
IG16.DAT 116' Compact
BG21.DAT 120' - 170' Five Box Girders
BG22.DAT 150' - 150'
IG21.DAT 140.5 '- 182.5' Nine Girder Lines
IG22.DAT 122' - 122'
2
IG23.DAT 180' - 167'
IG24.DAT 104' - 143'
IG25.DAT 261.5' - 357.25'
IG26.DAT 218' - 193' Five Girder Lines
16 GETTING STARTED
Exhibit 9a: Description of LRFD Simon Sample Input Files (con’t).
File Name Sub-Folder Girder Type Number of Spans Span Arrangement Additional Notes
BG31.DAT 100' - 140' - 100' Four Box Girders
BG32.DAT 150' - 150' - 110' Two Box Girders
IG31.DAT 298' - 298' - 203' Six Girders
IG32.DAT 140' - 200' - 115'
3
IG33.DAT 140' - 180' - 140'
IG34.DAT 3 @ 118'
IG35.DAT 200' - 350' - 200'
IG36.DAT 170' - 340' - 170' Haunched Girders
BG41.DAT 72' - 100' - 110' - 150' Two Box Girders
BG42.DAT …\4 Span\Box Girder\ Box Girder 210' - 280' - 280' - 210'
BG43.DAT 110' - 156' - 143' - 155' Four Box Girders
IG41.DAT 119' - 2 @ 148' - 119'
IG42.DAT 210' - 2 @ 435' - 210' Four Girders (L. Stiffened Web)
4
IG43.DAT 183' - 2 @ 226' - 183'
…\4 Span\Plate Girder\ Plate Girder 323.75' - 476.25' - 320' -
IG44.DAT Six Girder Lines
215'
IG45.DAT 145' - 2 @ 180' - 198' Four Girder Lines
Three Haunched Girders With Two
IG46.DAT 210' - 435' - 435' - 210'
Substringers
GETTING STARTED 17
If desired, the user can open one of these sample input files that most closely resembles the
geometry and configuration of the bridge under investigation, and simply edit the data
provided in the input forms as necessary (refer to Article 3). After editing, the file preferably
should be saved in a new file using the ‘Save Model As’ command described below (Article
2.2.2.4).
2.2.2.3 Save Model
Click on File and then on Save Model to save a new or a revised existing LRFD Simon model
(alternatively, hold down the ‘CTRL’ key and enter ‘S’).
When saving a new LRFD Simon model using this option, a Save Model As window will open up
when this option is chosen to allow the user to name the file and choose the folder in which the
model input file will be saved.
When saving a revised existing LRFD Simon model using this option, the current model input file
will be overwritten and the Save Model As window will not appear. If the user chooses not to
overwrite the current model input file and save the revised model in a new file instead, choose
the Save Model As option described below.
2.2.2.4 Save Model As
Click on File and then on Save Model As to save a new LRFD Simon model or to save a revised
existing LRFD Simon model in a new file.
When saving a new or revised existing model using this option, a Save Model As window will
open up when this option is chosen to allow the user to name the file and choose the folder in
which the model input file will be saved.
2.2.2.5 Save Input Verification
Click on File and then on Save Input Verification to save an .RTF file containing the input
consistency check report (see Article 2.2.3), which can be printed by the user using WORD.
When saving the input consistency check report using this option, a Save Model As window will
open up when this option is chosen to allow the user to name the file and choose the folder in
which the .RTF file will be saved.
2.2.2.6 Model Properties
After initially creating a new model, or after opening an existing LRFD Simon model input file,
click on File and then on Model Properties to open up the Model Properties window, which
18 GETTING STARTED
contains the data previously entered in the New Model window (Exhibit 4). The previously
entered data in this window may be edited using this option.
Click on ‘OK’ to save the entered data and exit the Model Properties window.
2.2.2.7 Close Model
Click on File and then on Close Model to close a new or existing LRFD Simon model input file
that has been previously opened without exiting the LRFD Simon program.
If this option is chosen for a new model or for an existing model that has been revised, and
either the Save Model or Save Model As option has not previously been chosen, a window
will open up asking the user if the model is to be saved. Choose Yes to save the model and
close the input file. If the model is a new model, a Save Model As window will open up to allow
the user to name the file and choose the folder in which the model input file will be saved. If
the model is an existing model that has been revised, the current model input file will be
overwritten and the Save Model As window will not appear. If the user chooses not to
overwrite the current model input file and save the revised model in a new file instead, click on
Cancel and choose the Save Model As option described above, and then choose this option
again. Choose No’ to close the model input file without saving the file.
If the Save Model or Save Model As option has previously been chosen and no further
revisions to the model are made, or if no revisions have been made at all to the model, the
model input file will simply be closed when this option is chosen.
2.2.2.8 Print Results
Click on File and then on Print Results to print the results for a new or existing LRFD Simon
model (alternatively, hold down the ‘CTRL’ key and enter ‘P’). The Print Results option is only
available when the results from an LRFD Simon analysis are available in the Input/Output
Window Pane on the right-hand side of the screen (Exhibit 13).
2.2.2.9 Exit
Click on File and then on Exit to exit the LRFD Simon program (alternatively, hold down the
‘ALT’ key and hit the F4 key).
If this option is chosen and a new model or an existing model that has been revised is open, and
either the Save Model or Save Model As option has not previously been chosen, a window
will open up asking the user if the model is to be saved before exiting the program. Choose
Yes to save the model and exit the LRFD Simon program. If the model is a new model, a Save
Model As window will open up to allow the user to name the file and choose the folder in which
the model input file will be saved. If the model is an existing model that has been revised, the
GETTING STARTED 19
current model input file will be overwritten and the Save Model As window will not appear. If
the user chooses not to overwrite the current model input file and save the revised model in a
new file instead, click on Cancel and choose the Save Model As option described above, and
then choose this option again. Choose No’ to exit the LRFD Simon program without saving the
file.
program will simply exit when this option is chosen.
2.2.3 Analyze Menu
The Analyze Menu Option is used to validate the input data on the LRFD Simon input forms or
run a new or existing model through the LRFD Simon analysis engine and produce results. The
LRFD Simon input forms must be completed before choosing this option, as described in Article
3.
Click on ‘Analyze’ and then ‘Validate Input’ at any time to perform consistency check results on
the data entered on the LRFD Simon input forms (Exhibit 10). The report of the input
consistency checks will appear in an Error Report Panel located in the Input/Output Window
Pane on the right-hand side of the screen described further below in Article 3.1. Whenever an
existing model is opened, the report of the latest consistency checks on the input data for the
model will appear immediately in the Error Report Panel. If no errors are detected and no
warnings are generated, the message “No Input Validation Errors or Warnings Detected” will
appear in the Error Report Panel and in the message bar at the bottom left of the screen.
Should any errors be detected in the input file or any warnings be generated, input file
validation error or warning messages will appear in the Error Report Panel and the message
“Input Validation Errors or Warnings Detected” will be displayed in the message bar. The
messages in the Error Report Panel will identify each error or warning and provide enough
information to assist the user to determine which input values are generating the error or
warning, how or why the value is incorrect or is generating a warning, and where the value can
be found. If desired, the input consistency check report can be printed by the user using the
File Menu Option ′Save Input Verification′ described above in Article 2.2.2.5. As errors are
corrected, they are removed from the list. When all errors are corrected, the message “No
Input Validation Errors or Warnings Detected” will be displayed in the Error Report Panel and in
the message bar.
The user can also validate the input data at any time by clicking on the Tool Strip button
‘Validate Input’ described further below in Article 2.3. The user can return to the Error Report
Panel at any time by clicking on “Model” in the Task Navigation Panel on the left-hand side of
the screen described further below in Article 3.1.
20 GETTING STARTED
The following checks are made whenever an input validation is performed:
1. The lower and upper limits on the input data are checked as defined in the Input Form
data descriptions given in Article 3;
2. The existence of at least one range on the Web, Top Flange, Bottom Flange, and Slab
Cross Section Information Forms (see Article 3.11) is verified;
3. Verification is made that the End Location on the first range of the Web, Top Flange,
Bottom Flange, and Slab Cross Section Information Forms (see Article 3.11) is greater
than zero, and that the End Location on the last range is the same as the span length for
the span under consideration;
4. Verification is made that the ranges on the Web, Top Flange, Bottom Flange, and Slab
Cross Section Information Forms (see Article 3.11) are in order moving from left to right
along the span under consideration;
5. Verification is made that the range values input on the Web, Top Flange, Bottom Flange,
and Slab Cross Section Information Forms (see Article 3.11) are less than the user-input
span length for the span under consideration;
6. Verification is made that the defined field-splice locations on the Field Splice Cross
Section Information Form (see Article 3.11.6) are in order moving from left to right along
the span under consideration, and that the defined field-splice locations are not within 5
percent of the span length from any support;
7. Verification is made that a value for the Distribution Factor Definition has been selected
on the Distribution Factors Form (see Article 3.3);
8. Verification is made that a value for the Design Vehicle Option has been selected on the
Loads Form (see Article 3.5);
9. Verification is made that the span lengths and cross-frame spacings on the Span
Information Form for each non-symmetrical span (see Article 3.10) are greater than
zero, and that the ratio of the span length to each cross-frame spacing is less than or
equal to 40 (the LRFD Simon analysis engine is limited to 40 brace points per span). The
top flange cross-frame spacing will not be checked if the corresponding ‘Top flange fully
braced’ dropdown box on the forms is set to ‘Yes’.
Click on Analyze and then Run Analysis to perform the LRFD Simon analysis (Exhibit 10). The
Run Analysis option is only available if a model input file has been opened. If the input file has
been modified prior to choosing this option, a window will open up indicating that the input file
has been modified and asking the user if it is desired to save the input file prior to running the
analysis. The LRFD Simon analysis will not be performed if a modified input file is not saved
prior to running the analysis. Choose Yes to save the model and perform the LRFD Simon
analysis. If the model is a new model, a Save Model As window will open up to allow the user
to name the file and choose the folder in which the model input file will be saved. If the model
is an existing model, the current model input file will be overwritten and the Save Model As
window will not appear. If the user chooses not to overwrite the current model input file and
save the revised model in a new file instead, click on No and choose the Save Model As
GETTING STARTED 21
option described above, and then choose this option again. Choose No’ if the input file is not
to be saved; in this case, the LRFD Simon analysis will not be performed.
LRFD Simon analysis will be performed when the Run Analysis option is chosen.
Exhibit 10: Analyze Menu Option: Validate LRFD Simon Input or Run LRFD Simon Analysis.
A validation of the input data on the LRFD Simon input forms will automatically be done prior to
running the analysis. Should errors be found in the program input during the validation or any
warnings be generated, a message will appear giving the user the option to proceed with the
analysis anyway if desired. The user should be aware that running the analysis with input
errors may cause program crashes or invalid program output.
When the LRFD Simon analysis successfully begins, a separate command prompt window (with
a black background) will open up indicating that the LRFD Simon analysis engine is running. If
the analysis completes successfully, a message to that effect will appear in the command
prompt window. The command prompt window will then close and the LRFD Simon results will
appear for examination in the Input/Output Window Pane on the right-hand side of the screen
(Exhibit 13). If an input error is detected that prevents the completion of a successful analysis,
a message will appear, the analysis will stop, the command prompt window will close and
partial LRFD Simon results will appear in the Input/Output Window Pane. It is suggested that
these partial results be reviewed in case there are any additional diagnostic messages provided.
If the a program results output file cannot be found, the message shown in Exhibit 11 will
appear in the Input/Output Window Pane to provide the user with several possible options.
22 GETTING STARTED
Exhibit 11: Error Message: If LRFD Simon Program Results Output File Not Found.
User Note: LRFD Simon supports the ability to open, edit and save model files
that are located or stored using a Universal Naming Convention (UNC) path.
UNC is a way to identify a shared file in a computer without having to specify or
know the storage device on which the file is located (e.g.
\\servername\sharename\SimonFiles\). However, model files specified on UNC
paths cannot be analyzed. In order to analyze model files, they must either be
stored locally or on a mapped drive (i.e. a path that starts with a drive letter such
as C:\).
2.3 Tool Strip Buttons
The Tool Strip Buttons (Exhibit 12) immediately underneath the Menu Bar on the LRFD Simon
input form (Exhibit 1) provide shortcuts that perform essentially the same functions as the
Menu Options previously described. In addition, a Search function is provided to allow the user
to quickly search through the LRFD Simon results (when available) to find specific keywords.
Placing the cursor and holding it over each Tool Strip Button for a few seconds will reveal the
function of each button.
GETTING STARTED 23
1 2 3 4 5 6 7 8 9 10
Exhibit 12: Tool Strip Buttons on the LRFD Simon Input Form.
The Tool Strip Buttons, from left to right in Exhibit 12, are as follows:
1 New Model...
2 Save Model
3 Open Model…
4 Close Model
5 Model Properties
6 Validate Input
7 Run Analysis…
8 Print Results (will only be active when program output is available)
9 Search (will only be active when program output is available)
10 View LRFD Simon User's Guide
For the functions of Tool Strip Buttons 1 through 8, refer to the previous descriptions under
Menu Options.
Tool Strip Button 9 (Search) allows the user to perform a search through the LRFD Simon results
in the Input/Output Window Pane (Exhibit 13) after an analysis has been completed and
program output is available. When this button is selected, a search window opens up and
prompts the user to enter a word or phrase to locate in the output results. The user can
choose whether or not to have the whole word matched only, to match the case, and/or to
highlight all matches by checking the appropriate boxes in the window. Buttons are also
available to allow the user to move to the previous or next occurrence of the word or phrase if
applicable. A message will appear at the bottom of the search window if no matches are found.
Click the box in the upper right-hand corner of the search window to close the window.
Tool Strip Button 10 allows the user to bring up a searchable .PDF of this LRFD Simon User’s
Guide, which can then be printed.
24 GETTING STARTED
3 INPUT FORMS
3.1 General
There are three main regions within the LRFD Simon user interface screen: 1) the Menu Bar and
Tool Strip Buttons at the top; 2) the Task Navigation Pane on the left; and 3) the Input/Output
Window Pane on the right (Exhibit 13).
Menu Bar
Tool Strip Buttons
Input/Output Window Pane
Task Navigation Pane
Exhibit 13: LRFD Simon User Interface Screen.
The necessary data for an LRFD Simon run are input by the user on a series of input forms. The
typical workflow is to begin at the top of the Task Navigation Pane with the General Properties
Form, which is the first form to appear in the Input/Output Window Pane whenever a new
model is opened (Exhibit 13). After completing the General Properties Form, the user moves
down through each of the forms in the Task Navigation Pane in succession by clicking on each
form and inputting the appropriate values on that form in the Input/Output Window Pane.
When the necessary data have been entered on all of the forms up through the Result Controls
Form, the user should save the data using one of the appropriate Menu Options or Tool Strip
Buttons and proceed to run the analysis, if desired. The analysis may be executed using either
the Analysis Menu Option, or the appropriate Tool Strip Button, as described above. Once the
analysis is completed, the results are displayed in the Input/Output Window Pane.
INPUT FORMS 25
When an existing model is opened, all input forms will contain the latest data that were
entered and saved for that model. The report of the latest consistency checks on the input data
for the model will appear immediately in the Error Report Panel located in the Input/Output
Window Pane. The data in each form may be edited by clicking on the appropriate form in the
Task Navigation Pane and performing the necessary edits to the form in the Input/Output
Window Pane. The user should then save the revised model and proceed to validate the input
or run the analysis, if desired, as described above. Results from the latest analysis may be
viewed in the Input/Output Window Pane by clicking on Results at the bottom of the Task
Navigation Pane.
Each of the LRFD Simon input forms on the Task Navigation Pane is described in more detail
below starting with the General Properties Form, and proceeding in succession through all of
the forms. The input items on each form are described in tables after each exhibit showing a
sample filled-in form. Where a default value is indicated in the table, this indicates the value
that is assumed by LRFD Simon for that particular input item if no input is provided. Where a
default value is not indicated, either an input value or a user-selection is required for that
particular input item unless otherwise indicated. Permissible upper and lower limits on the
input values are indicated in the table for some of the input items. Where an article number is
indicated without the word AASHTO in front in the Remarks column of the table, this refers to
an article number within this User’s Guide where further more detailed information on a
particular input item may be found. If the words AASHTO LRFD are in front of the article
number, consult that particular article number in the AASHTO LRFD Bridge Design Specifications
for further information.
26 INPUT FORMS
3.2 General Properties Form
3.2.1 General
The General Properties Form is used to identify the job, beam type (I or box girder), number of
spans, number of girders, number of design lanes, run option (analysis and evaluation for one
design cycle only, or iterative analysis-evaluation-design cycles), user-defined parameters to
control the iterative analysis-evaluation-design process, deck reinforcement location and deck
haunch thickness data, and the average daily truck traffic in a single lane and service life for
fatigue design. A sample filled-in General Properties Form is shown in Exhibit 14. Article 3.2.2
contains the table describing the data to be entered in the General Properties Form.
Exhibit 14: General Properties Form.
INPUT FORMS 27
3.2.2 General Properties Form Data
Lower Upper
Input Item Default Remarks
Limit Limit
Enter the problem description. Up to 79
Comments, line 1
characters – may be left blank
Enter the problem description (continued). Up
Comments, line 2
to 79 characters – may be left blank
Enter the problem description (continued). Up
Comments, line 3
to 79 characters – may be left blank
Choose the beam type.
Options:
I-Girder
Box Girder
Beam type
When a Box Girder is chosen, a Box Girder
Properties Form (Article 3.9) will appear in the
Task Navigation Pane immediately after the
Shear Stud Properties Form.
Enter the number of spans in the bridge or unit
Number of spans 1 12 under investigation. Include spans that are later
declared symmetrical (Article 3.10.2)
For I-girder designs, enter the number of I-
girders in the cross-section. For box girder
Number of girders 1 20 4
designs, enter the number of boxes in the cross-
section
Enter the number of design lanes (AASHTO LRFD
Number of traffic Article 3.6.1.1.1) – used to calculate the
1 8 2
lanes distribution factor for live load deflection
(Article 3.3.1).
Choose the run option.
Options:
LRFD Design (see Article 5.1.2)
Run option LRFD Analysis (see Article 5.1.1)
If the LRFD Analysis run option is chosen for a

box girder, the bottom flange will always be
unstiffened.
28 INPUT FORMS
Lower Upper
Limit Limit
Enter the redesign performance ratio. If the
performance ratio is below 1.0, and a non-
fatigue behavior constraint is encountered at a
Redesign
0.1 0.99 0.90 cross-section, a redesign is made only if the
performance ratio
performance ratio is below this value – this item
is only active if the LRFD Design run option is
chosen (Article 5.1.2)
Enter the maximum permissible performance
ratio. If the performance ratio is above this
Maximum
0.95 1.10 1.00 value, redesign is mandatory– this item is only
performance ratio
active if the LRFD Design run option is chosen
(Article 5.1.2)
Enter the minimum permissible flange thickness.
Not applicable to a box girder bottom flange if a
Minimum flange
0.3125 in. 4 in. 0.3125 in. different minimum bottom flange thickness is
thickness, in
entered via the Box Girder Properties form
(Article 3.9).
Maximum plate
0.3125 in. 4 in. 4 in. Enter the maximum permissible plate thickness.
thickness, in
Enter the distance from the bottom of the deck
slab to the center of gravity of the longitudinal
Distance from slab deck reinforcement. Locates the centroid of the
bottom to cg of 1.5 in. 12 in. 0 in. longitudinal reinforcement with respect to the
reinforcement, in steel section. If the longitudinal reinforcement is
not to be considered in the computation of the
composite section properties, enter 0.
Enter the distance from the bottom of the deck
slab to the top of the girder web. Locates the
deck slab with respect to the steel section (i.e.
Distance from slab
defines the depth of the concrete deck haunch).
bottom to web top, 0 in. 12 in. 0 in.
If the bridge is non-composite or to ignore the
in
haunch, enter 0. The area of the deck haunch is
not included in the calculation of the composite
section properties.
Average daily truck Enter the average daily truck traffic in a single
0 10000 0
traffic, single lane lane (AASHTO LRFD Article 3.6.1.4.2)
Enter the number of years that a detail is
Fatigue service life, 200
1 year 75 years expected to resist the assumed traffic loads
years years
without fatigue cracking
INPUT FORMS 29
3.3 Distribution Factors Form
3.3.1 General
The Distribution Factors Form is used to either: 1) have LRFD Simon internally compute the
governing live-load distribution factors for moment and shear for both single-lane and multiple-
lane loading based on data supplied by the user (Program Defined - Exhibit 15); or 2) allow the
user to calculate and input the governing live-load distribution factors for moment and shear
for both single-lane and multiple-lane loading (User Defined - Exhibit 16). Note that the
distribution factors are to be entered in units of lanes. Article 3.3.2 contains the table
describing the data to be entered in the Distribution Factors Form.
Multiple presence factors are presumed included in the User Defined distribution factors, and
are considered (as necessary) in the Program Defined Distribution Factors.
The Program Defined Distribution Factor input data (Exhibit 15) are only applied in the
computation of the distribution factors for I-girders. If ′Program Defined′ is selected for a box
girder, LRFD Simon will compute the distribution factors internally from the live-load
distribution factor equation given for steel box girders specified at the bottom of AASHTO LRFD
Table 4.6.2.2.2b-1. Although the Program Defined Distribution Factor input data are not used
for the computation of the distribution factors for box girders, data must still be entered if
′Program Defined′ is selected in order for LRFD Simon to run; the data will be ignored.
User Notes:
1) The User Defined single-lane distribution factors for moment and shear
are NOT to be divided by the multiple presence factor of 1.2 for one-lane
loaded; LRFD Simon does this operation internally for all fatigue-related
investigations of I-girders. The Program Defined distribution factors for a
single lane that are output for moment and shear are also NOT divided by
the multiple presence factor of 1.2. This is not done (and should not be
done) for box girders as the multiple presence factor of 1.2 was not
considered in the original development of the live load distribution factor
equation for steel box girders specified at the bottom of AASHTO LRFD
Table 4.6.2.2.2b-1.
2) The distribution factor used for computing the live-load deflection is

computed internally by LRFD Simon as:
where m is equal to the appropriate multiple presence factor, NL is the

number of design lanes and Ng is the number of girders in the cross-
section.
30 INPUT FORMS
3) The rigid cross-section equation (AASHTO LRFD Eq. C4.6.2.2.2d-1) is NOT
considered in the Program Defined distribution factors for exterior I-
girders for moment or shear.
For the Program Defined Distribution Factors for I-girders, the longitudinal stiffness parameter,
Kg, in the distribution factor equations is computed at 20th points along each span. An average
value of Kg is then computed for each span by summing the computed values at each 20th point,
plus the value at the beginning of the span, and dividing the sum by 21. A weighted average
value of Kg for the girder, which is then used in the distribution factor calculation, is then
computed by multiplying each span value by its corresponding span length, adding the resulting
values for each span together, and then dividing the sum by the total girder length. If any of
the ranges of applicability for the live load distribution factors given in the last column of the
distribution factor tables in AASHTO LRFD Article 4.6.2.2.2 are violated, LRFD Simon computes
the distribution factor using the lever rule.
When computing the distribution factors for I-girders, the length, L, using in the computation of
Kg is taken as the length of the span for which the moment is being calculated for positive
flexure, and as the average length of the two adjacent spans for negative flexure.
When the input girder skew angle is not zero, the skew correction factor for I-girders is
computed internally for each span, and the largest value is applied to the shear distribution
factor. The skew correction factor for bending moment is not computed or applied.
For box girders, if the User Defined distribution factors are left blank (or entered as zero), LRFD
Simon will compute the distribution factors internally from the live-load distribution factor
equation given for steel box girders specified at the bottom of AASHTO LRFD Table 4.6.2.2.2b-1.
The same equation is used to compute the distribution factor for bending moment and shear
for both interior and exterior girders. When computing the distribution factor for a single lane,
NL is set equal to 1.0 in the equation. The special restrictions specified in AASHTO LRFD Article
6.11.2.3 must be satisfied in order to use the AASHTO live-load distribution factor given for
steel box girders specified at the bottom of AASHTO LRFD Table 4.6.2.2.2b-1 (and hence LRFD
Simon). As specified in AASHTO LRFD Article 6.11.1.1, when these restrictions are satisfied, this
also permits: 1) shear due to St. Venant torsion to be neglected in the design of the girders and
shear connectors, and 2) transverse bending stresses and longitudinal warping stresses due to
cross-section distortion to be neglected. LRFD Simon will automatically check some of these
restrictions, as follows, and report the results of these checks:
 Cross section must consist of two or more single-cell box sections.
 Distance center-to-center of flanges of adjacent boxes, a, taken at midspan must be no

greater than 120 percent nor less than 80 percent of the distance center-to-center of
the flanges of each adjacent box, w. (See AASHTO LRFD Figure 6.11.2.3-1).
 The inclination of the web plates to a plane normal to the bottom flange must not
exceed 1 to 4.
INPUT FORMS 31
 The bottom flange must be fully effective over the entire length of the girder. The
bottom flange is fully effective if the bottom flange width does not exceed 20 percent of
the effective span length.
The user is responsible for ensuring that the following remaining restrictions are satisfied:
 Bearing lines must not be skewed.
 The bridge must be straight.
 If nonparallel box sections are used, the distance center-to-center of adjacent flanges at
supports must neither be greater than 135 percent nor less than 65 percent of the
distance center to center of the flanges of each adjacent box.
 The cantilever overhang of the concrete deck must not be greater than either 60
percent of the average distance between the centers of the top steel flanges of adjacent
box sections or 6 feet.
The ratio, NL/Nb, related to the lateral distribution of loads for moment in box girders is not
permitted to be less than 0.5 or greater than 1.5 (AASHTO LRFD Table 4.6.2.2.2b-1). The
designer may generate a ratio that is outside these limits. If the designer does, the design
process continues with the distribution factor instead computed by the lever rule. The skew
correction factor is set internally to 1.0 in LRFD Simon for box girders.
If User Defined distribution factors are entered for a box girder, they will be used in lieu of
the AASHTO distribution factor equation.
32 INPUT FORMS
Exhibit 15: Distribution Factors Form for Program Defined Distribution Factors.
Exhibit 16: Distribution Factors Form for User Defined Distribution Factors.
INPUT FORMS 33
3.3.2 Distribution Factors Form Data
Lower Upper
Limit Limit
Choose whether the distribution factors are to be
computed internally by LRFD Simon, or if they are to
be input by the user (see below).
Distribution factor
definition
Options:
Program Defined
User Defined
Program Defined Distribution Factors
(data for I-Girders only; for box girders, data must still be entered if factors are to be computed using the
AASHTO distribution factor equation for box girders, but this data will be ignored in the computation of the
factors.)
Enter the largest support skew angle measured
from the normal to the girder tangent (0 degrees =
Girder skew, -60 60
0 degrees no skew). User may enter a positive or negative
degrees degrees degees
value, but the absolute value is used internally in
the computation of the skew correction factor.
Enter the spacing from center of girder to center of
Girder spacing, ft 3 ft 25 ft
girder.
Enter the distance from the centerline of the
Distance from web exterior girder web at the deck slab level to the
-10 ft 15 ft
to curb, de, ft interior edge of the curb or parapet (AASHTO LRFD
Article 4.6.2.2.2).
Choose whether the distribution factors are to be
computed for an exterior or an interior girder.
Girder location Interior
Options:
Exterior
Interior
User Defined Distribution Factors
(for box girders, if 0. or blank, factors will be computed using the AASHTO distribution factor equation for box
girders; otherwise, the input factors will be used.)
Enter the governing moment distribution factor for
a single lane. For interior I-girders, refer to AASHTO
User-Input Moment
LRFD Article 4.6.2.2.2b. For exterior I-girders, refer
Distribution Factor, 0 2
to AASHTO LRFD Article 4.6.2.2.2d. For skewed I-
Single lane, lanes
girder bridges, see also AASHTO LRFD Article
4.6.2.2.2e.
User-Input Moment
Enter the governing moment distribution factor for
Distribution factor, 0 2
multiple lanes. See above.
Multiple lane, lanes
34 INPUT FORMS
Enter the governing shear distribution factor for a
single lane. For interior I-girders, refer to AASHTO
User-Input Shear
LRFD Article 4.6.2.2.3a. For exterior I-girders, refer
to AASHTO LRFD Article 4.6.2.2.3b. For skewed I-
Single lane, lanes
girder bridges, see also AASHTO LRFD Article
4.6.2.2.3c.
User-Input Shear
Enter the governing shear distribution factor for
multiple lanes. See above.
Multiple lane, lanes
INPUT FORMS 35
3.4 Material Properties Form
3.4.1 General
The Material Properties Form is used to enter some specific input parameters related to
material properties (e.g. the modular ratio, slab compressive strength and reinforcement and
stiffener yield strengths), miscellaneous information related to fatigue checks, and whether or
not the deck slab meets the criteria specified in AASHTO LRFD Article 6.10.1.7. A sample filled-
in Material Properties Form is shown in Exhibit 17. Article 3.4.2 contains the table describing
the data to be entered in the Material Properties Form. The miscellaneous information related
to fatigue checks and the AASHTO LRFD Article 6.10.1.7 option is discussed in more detail in this
table.
Exhibit 17: Material Properties Form.
36 INPUT FORMS
3.4.2 Material Properties Form Data
Lower Upper
Input Item Limit Limit Default Remarks
Enter the modular ratio given by AASHTO LRFD Eq.
Modular ratio, n 0 10 0
6.10.1.1.1b-1. If the bridge is non-composite, enter 0.
Enter the specified minimum compressive strength of the
Slab compressive deck concrete at 28 days. A warning is given if the input
1500 psi 12000 psi 0 psi
strength, psi value is not consistent with n, as specified in AASHTO LRFD
Article C6.10.1.1.1b. If the bridge is non-composite, enter 0.
Enter the specified minimum yield strength of the
Reinforcement
20 ksi 120 ksi 0 ksi longitudinal deck reinforcement. If the longitudinal deck
yield strength, ksi reinforcement is not considered, enter 0.
Longitudinal Enter the specified minimum yield strength of web
stiffener yield 18 ksi 140 ksi 36 ksi longitudinal stiffeners (for clarity, a distinction is made
strength, ksi between web and bottom flange longitudinal stiffeners).
Transverse and Enter the specified minimum yield strength of transverse
bearing stiffener 18 ksi 140 ksi 36 ksi and bearing stiffeners.
yield strength, ksi
Choose the concrete type.
Options:
Normal weight concrete
Normal
Concrete type Sand lightweight concrete
weight All lightweight concrete
The concrete type is used to determine the modulus of

rupture of the deck concrete.
Choose the steel surface condition.
Options:
Weathering steel
Steel surface Weatherin
Painted steel
condition g
The steel surface condition determines if the base-metal
fatigue check is based on AASHTO fatigue Category A
(painted steel) or Category B (weathering steel).
Choose the cross-frame/diaphragm connection plate type.
Options:
Welded connection plates
Bolted connection plates
Connection plate
Welded
type The cross-frame/diaphragm connection plate type
determines if the fatigue check at the inside face of the
tension flange at a section is based on AASHTO fatigue
Category B (bolted connection plates) or Category C' (welded
connection plates).
INPUT FORMS 37
Choose whether or not the deck slab satisfies the criteria
specified in AASHTO LRFD Article 6.10.1.7.
Options:
Yes: if the slab is connected to the girder with shear
studs throughout, and meets the criteria for
the minimum negative flexure concrete deck
reinforcement specified in AASHTO LRFD
Article 6.10.1.7
No: if one or both of the preceding criteria are not
met
If Yes is chosen, LRFD Simon will consider the slab effective

for both positive and negative flexure for the calculation of
dead load and live load stresses and live load stress ranges
for fatigue design at all sections in the member due to loads
applied to the composite section (see AASHTO LRFD Article
6.6.1.2.1). The long-term (3n) composite section is used for
composite dead loads, and short-term (n) composite section
is used for live loads.
If Yes is chosen and LRFD Simon determines internally that

Slab meet 6.10.1.7 No the Service II tensile stress in the slab at the section under
criteria consideration is less than 2fr, where fr is the modulus of
rupture of the concrete specified in AASHTO LRFD Article
6.10.1.7, the slab will also be considered effective for both
positive and negative flexure for the calculation of the
Service II flexural stresses in the steel girder at the section
under consideration due to loads applied to the composite
section (see AASHTO LRFD Article 6.10.4.2.1). The long-term
(3n) composite section is used for composite dead loads, and
short-term (n) composite section is used for live loads. If the
Service II tensile stress in the slab at the section under
consideration is greater than 2fr, the slab will not be
considered effective for negative flexure for the calculation
of the Service II flexural stresses in the steel girder at the
section under consideration due to loads applied to the
composite section. Stresses due to negative flexure in this
case will be computed using the section consisting of the
steel section plus the longitudinal reinforcement, or the steel
section alone, as applicable.
If No is chosen, the slab will not be considered effective for

negative flexure for the calculation of dead load and live load
stresses and live load stress ranges for fatigue design, and for
the calculation of Service II flexural stresses in the steel
girder at all sections in the member, due to loads applied to
the composite section. Stresses due to negative flexure in
this case will be computed using the section consisting of the
steel section plus the longitudinal reinforcement, or the steel
38 INPUT FORMS
3.5 Loads Form
3.5.1 General
The Loads Form is used to enter load information; specifically, the magnitudes of the long-term
uniform dead loads that are to be applied to the composite section, and also live load
information. A sample filled-in Loads Form is shown in Exhibit 18. Article 3.5.4 contains the
table describing the data to be entered in the Loads Form.
3.5.2 Long-Term Composite Dead Loads
Long-term dead loads applied to the composite section include component dead loads (DC2
loads - e.g. parapets, railings, sound walls), and future wearing surface and utility loads (DW
loads). These loads are applied to the 3n or long-term composite section in the analysis and
when determining section stresses to account for the effects of concrete creep.
User Notes:
1) The uniform dead loads that are entered should be the loads assumed acting on the girder
under consideration and NOT the total load acting on the bridge cross-section. For box
girders, enter the total load assumed acting on the box under consideration and NOT the
load on each individual web.
2) A reasonable distribution of the DC2 and utility loads to the individual girders in the cross-
section should be assumed if possible. Future wearing surface loads may be assumed
distributed equally to each girder in the cross-section.
3) Utility loads applied to the non-composite section may be input as uniform full-length or
partial-length non-composite component dead loads, as applicable, on the Span
Information Form (Article 3.10).
3.5.3 Live Load Information
Live load information is also provided on this form. The user can select either an analysis that
develops an envelope of the live-load effects caused by the HL-93 design live load (see also
Article 5.2) and a user-defined design vehicle, or an analysis that develops an envelope of the
live-load effects caused by the user-defined design vehicle only (see the Design Vehicle Option
below). If the first option is selected and there is no design vehicle defined by the user, live-
load effects will be developed for the HL-93 design live load only. An envelope of live-load
effects due to the fatigue live load is also included with either design vehicle option. User-
defined design trucks can have up to 40 axles with variable axle spacings, and are defined on a
subsequent input form (see Article 3.6). A user-defined design lane live load can also be
INPUT FORMS 39
included. Live loads are applied to the n- or short-term composite section in the analysis and
when determining section stresses.
Other live load related parameters that may be input on this form include the factor used to
check live load deflection, which defaults to 800 (corresponding to a live load deflection limit of
L/800), a uniform pedestrian live load applied to the girder under consideration, and the
dynamic allowance (impact) factor to be applied to the load effects due to the design truck,
design tandem or user-defined design truck, which defaults to 1.33, and to the load effects due
to the fatigue live load, which defaults to 1.15.
The loads effects due to the pedestrian live load (when entered) are added to the vehicular load
effects by LRFD Simon, and the combined effects are then factored. The dynamic allowance
(impact) factor is not applied to the pedestrian live load effects. No distribution factors are
applied to the pedestrian live load effects; therefore, the user should enter the pedestrian live
load acting on the girder under consideration.
Exhibit 18: Loads Form.
40 INPUT FORMS
3.5.4 Loads Form Data
Lower Upper
Limit Limit
Enter the uniform component dead load, DC2 load,
Composite uniform -10000 10000
0 supported by the long-term composite section (e.g.
dead load, lb/ft lb/ft lb/ft
parapets, railings, sound walls, etc.).
Utility uniform -10000 10000 Enter the uniform utility load, DW load, supported
0
dead load, lb/ft lb/ft lb/ft by the long-term composite section.
Future wearing Enter the uniform future wearing surface load, DW
-10000 10000
surface uniform 0 load, supported by the long-term composite
lb/ft lb/ft
dead load, lb/ft section.
Choose the design vehicle option (see the
description in Article 3.5.3).
Options:
Design vehicle
HL93 / User Defined Design Vehicle
option
User Defined Design Vehicle only
Note: Both options also include the LRFD fatigue

live load.
Enter the factor for checking the live load
Live load deflection
100 2000 800 deflection. Refer to AASHTO LRFD Article 2.5.2.6.2
factor
and Article 5.2.
Enter the uniform pedestrian live load acting on the
Pedestrian live -10000 10000
0 girder under consideration (enter 0 for no
load, lb/ft lb/ft lb/ft
pedestrian live load). See Article 3.5.3.
Enter the dynamic load allowance (impact) to be
Dynamic load
applied to the load effects due to the design truck
allowance, design 1.0 2.0 1.33
and the design tandem, or to the user-defined
vehicle
design truck
Dynamic load Enter the dynamic load allowance (impact) to be
allowance, fatigue 1.0 2.0 1.15 applied to the load effects due to the fatigue live
vehicle load
INPUT FORMS 41
3.6 User Defined Design Vehicle Properties Form
3.6.1 General
The User Defined Design Vehicle Properties Form may be optionally used to enter information
about a user-defined design vehicle to be considered in the analysis/design. This form need not
be filled out if a user-defined design vehicle is not to be considered. The load effects due to the
user-defined design vehicle defined on this form will be considered according to the Design
Vehicle Option that is selected on the Loads Form (see Article 3.5.3). A sample blank User
Defined Design Vehicle Form is shown in Exhibit 19. Article 3.6.2 contains the table describing
the data to be entered in the User Defined Design Vehicle Form.
A user-defined design truck can be defined having up to 40 axles with constant and/or variable
axle spacings. An option is provided to ignore axle loads in the analysis that do not contribute
to a given force effect. A user-defined design lane live load can also be defined acting in
conjunction with the design truck; the user-defined design lane live load will not be considered
acting by itself. The single-lane and/or multiple-lane distribution factors can be applied
separately to the load effects due to the user-defined design truck and design lane live load, or
both can be considered. When both are to be considered, the largest value is applied. The
dynamic load allowance (impact) input for the design vehicle on the Loads Form (Article 3.5) is
applied to the load effects due to the user-defined design truck only.
User Note: To apply load combination Strength II to the user-defined design vehicle at the strength
limit state, multiply the input loads by a factor of 1.35/1.75. The effective live load factor applied for
checking the Service II load combination at the service limit state will then be 1.3 * (1.35/1.75) = 1.003.
42 INPUT FORMS
Exhibit 19: User Defined Design Vehicle Properties Form.
INPUT FORMS 43
3.6.2 User Defined Design Vehicle Form Data
Lower Upper
Choose the live load distribution factor to be
applied to the load effects due to the user-defined
design truck (i.e. single lane, multiple lane or both)
– Exhibit 20a.
Distribution factor
Multiple Options:
type for truck
Single
Multiple
Both
When Both is chosen, the largest value is applied.

Choose the live load distribution factor to be
applied to the load effects due to the user-defined
design lane load (i.e. single lane, multiple lane or
both) – Exhibit 20b.
Distribution factor
Multiple Options:
type for lane
Single
Multiple
Both
When Both is chosen, the largest value is applied.

Enter a uniform user-defined design lane live load
Lane live load, to be applied in combination with the user-defined
0 kips/ft 3 kips/ft 0.0
kips/ft design truck load axles (the user-defined design
lane live load may not be applied by itself).
Choose whether or not the effects of all axle loads
are to be included in calculating a given live load
effect – Exhibit 20c.
Options:
Yes: if the effects of all axle loads are to be
Include all axles Yes
included in calculating a given live
load effect
No: if the axle loads that do not contribute
to the given live load effect are to be
neglected
Enter the magnitude of the axle load for the user-

Axle load, kips 0 kips 100 kips 0 defined design truck load (up to 40 axles may be
included).
44 INPUT FORMS
Lower Upper
Enter the spacing from axle n to axle (n+1) for the
Axle spacing, ft 0 ft 100 ft 0
user-defined design truck load.
A B
C
Exhibit 20: User Defined Design Vehicle Properties Form – Distribution Factor & Axle Options.
INPUT FORMS 45
3.7 Transverse Stiffener Properties Form
3.7.1 General
The Transverse Stiffener Properties Form is used to enter a user-input maximum web
transverse stiffener spacing for the stiffeners, and to indicate whether or not the web
transverse stiffeners are located on one side of the web or on both sides of the web, which is
necessary information for the design of the stiffeners. A sample filled-in Transverse Stiffener
Properties Form is shown in Exhibit 21. Article 3.7.2 contains the table describing the data to
be entered in the Transverse Stiffener Properties Form.
The required spacing and design of the web transverse stiffeners is only performed by LRFD
Simon if the input girder design is acceptable when the LRFD Analysis run option (Article 5.1.1)
is chosen on the General Properties Form (Article 3.2), or if a successful convergence of the
girder design iterations is completed when the LRFD Design run option (Article 5.1.2) is chosen.
In the AASHTO LRFD Specifications (Article 6.10.9.1), web stiffener spacings up to a maximum of
3D are permitted for interior stiffened panels without web longitudinal stiffeners, and up to a
maximum of 1.5D for interior stiffened panels with web longitudinal stiffeners, where D is the
total web depth. For box girders with sloping webs, D is measured along the web slope. Web
stiffener spacings for end panels with or without web longitudinal stiffeners are limited to 1.5D
(Article 6.10.9.3.3). LRFD Simon will limit the stiffener spacings to the smaller of these values, as
applicable, or the maximum web transverse stiffener spacing input by the user on this form.
46 INPUT FORMS
Exhibit 21: Transverse Stiffener Properties Form.
INPUT FORMS 47
3.7.2 Transverse Stiffener Properties Form Data
Lower Upper
Limit Limit
Maximum
spacing
permitted
by AASHTO
Maximum
LRFD Enter the desired maximum web transverse
transverse stiffener 3 in 864 in
Articles stiffener spacing.
spacing, in
6.10.9.1 and
6.10.9.3.3,
as
applicable
For the design of the web transverse stiffeners,
choose whether or not the stiffeners are located
on only one side of the web, or in pairs on both
sides of the web – Exhibit 22.
One sided
transverse Options:
stiffeners Yes: if the transverse stiffeners are located
on only one side of the web
No: if the transverse stiffeners are in pairs
on both sides of the web
Exhibit 22: Transverse Stiffener Properties Form – One-Sided Stiffener Option.
48 INPUT FORMS
3.8 Shear Stud Properties Form
3.8.1 General
The Shear Stud Properties Form is used to request that LRFD Simon perform a stud shear
connector design, and to enter information needed by the program in order to perform the
design. A sample filled-in Shear Stud Properties Form is shown in Exhibit 23. Article 3.8.2
contains the table describing the data to be entered in the Shear Stud Properties Form.
Should the user request a stud shear connector design on this form, the design is only
performed by LRFD Simon if the input girder design is acceptable when the LRFD Analysis run
option (Article 5.1.1) is chosen on the General Properties Form (Article 3.2), or if a successful
convergence of the girder design iterations is completed when the LRFD Design run option
(Article 5.1.2) is chosen. The pitch of the shear connectors is determined to satisfy fatigue limit
state requirements and is also checked for strength limit state requirements. The user is
referred to Article 5.3.7 for further discussion on the shear-connector design procedure in LRFD
Simon.
Exhibit 23: Shear Stud Properties Form.
INPUT FORMS 49
3.8.2 Shear Stud Properties Form Data
Lower Upper
Limit Limit
Choose whether or not to have LRFD Simon perform
a stud shear connector design after an acceptable
girder design has been detected – Exhibit 24.
Options:
Yes: have LRFD Simon perform a stud
Shear connector shear connector design after an
design acceptable girder design has been
determined (see Article 5.3.7)
No: do not have LRFD Simon perform a
stud shear connector design
If No is chosen, the remainder of the information on

this form may be left blank.
For an I-girder design only, optionally enter the
distance from the interior support to the nearest
Distance from
shear connector to have LRFD Simon omit the studs
interior support to
0 ft 50 ft 0 ft in a region up to 5 percent of the span on either
nearest shear
side of each interior support to eliminate potential
connector, ft
fatigue problems with the stud / flange connections
in that region (see Article 5.3.7).
Enter the deck concrete unit weight to be used in
Concrete weight
AASHTO LRFD Eq. 5.4.2.4-1 to compute the elastic
used to calculate
100 pcf 200 pcf 150 pcf modulus of the concrete, Ec. The factor K1 in
concrete elastic
AASHTO LRFD Eq. 5.4.2.4-1 is assumed equal to 1.0
modulus, lb / ft3
by LRFD Simon.
Enter the desired pitch increment of the studs
Desirable pitch (between 1 in. and 6 in.). LRFD Simon will stop if
1 in 6 in 3 in
increment, in the required pitch is less than the desired pitch
increment.
Stud diameter, in 0.5 in 2.0 in 0.875 in Enter the stud diameter.
Stud length, in 2 in 14 in 4 in Enter the length of the studs.
Studs per row 2 6 3 Enter the number of studs per row.
50 INPUT FORMS
Exhibit 24: Shear Stud Properties Form – Shear Connector Design Option.
INPUT FORMS 51
3.9 Box Girder Properties Form
3.9.1 General
The Box Girder Properties Form only appears in the Task Navigation Pane when the user selects
a Box Girder beam type on the General Properties Form (Article 3.2). This form is used to enter
specific geometry and bottom flange information needed by LRFD Simon in order to perform
the analysis/design of the box girder. A sample filled-in Box Girder Properties Form is shown in
Exhibit 25. Article 3.9.2 contains the table describing the data to be entered in the Box Girder
Properties Form.
Exhibit 25: Box Girder Properties Form.
52 INPUT FORMS
3.9.2 Box Girder Properties Form Data
Lower Upper
Horizontal offset
Defines the geometry of a sloping web. Enter 0.
ratio of web plate 0 0.9 0
for a vertical web; enter 0.25 for a 1:4 slope.
to vertical
Enter the spacing between top flanges on two
adjacent box girders (i.e. the dimension "a"
shown in AASHTO LRFD Figure 6.11.2.3-1). This
value is used to determine the applicability of
the AASHTO live load distribution factor for steel
box girders (Article 3.3.1).
Box girder spacing,

1 ft 30 ft
ft
Choose the maximum number of compression

flange longitudinal stiffeners per box to be
considered when designing the box girder.
Maximum number Options:

of compression 0
0
flange longitudinal 1
stiffeners per box 2
Choose 0 for an unstiffened bottom flange. A

maximum of two compression flange
longitudinal stiffeners will be considered.
Enter the minimum tee area for the compression
flange longitudinal stiffener(s). The minimum
and maximum tee areas may optionally be used
to control the many possible combinations of
bottom flange thickness and flange stiffener
Minimum tee area, Smallest tee
2.0 in2 45.0 in2 area. Refer to Article 5.3.4.2 for additional
in2 area
information.
If both the minimum and maximum tee areas

are selected as the same, only that tee size is
considered.
INPUT FORMS 53
Lower Upper
Enter the maximum tee area for the
compression flange longitudinal stiffener(s). The
minimum and maximum tee areas may
optionally be used to control the many possible
combinations of bottom flange thickness and
Maximum tee area, Largest tee
2.0 in2 45.0 in2 flange stiffener area. Refer to Article 5.3.4.2 for
in2 area
additional information.
If both the minimum and maximum tee areas

are selected as the same, only that tee size is
considered.
Enter the redesign performance ratio for the
Redesign
Value from bottom flange in compression. This ratio may be
performance ratio
General used to reduce the number of design cycles since
for the bottom 0.1 0.99
Properties redesign of the bottom flange of a box girder
flange in
Form may be more sensitive to a change in plate
compression
thickness than that for an I-girder.
Enter the minimum bottom flange thickness.
Minimum bottom This input value will override the value of
0.3125 in 4 in 0.375 in
flange thickness, in. minimum flange thickness entered on the
General Properties Form (Article 3.2).
Enter the width of the bottom flange extending
beyond the face of the webs of the box girder.
Box girder bottom
Enter the width for only one side. (i.e. if the
flange "lip" 0 in 12 in
bottom flange extends 2" to the left of the face
dimension, in.
of the left web and 2" to the right of the face of
the right web, enter 2 here)
54 INPUT FORMS
Lower Upper
Choose a flag for the bottom flange width
applicability (effective width) checks (AASHTO
LRFD Article 6.11.1.1) – Exhibit 26.
Options:
Stop if failure: the program does the
bottom flange effective width
applicability checks and stops if the
Flag for bottom width fails
flange width Use full width: the program does the
applicability checks checks, warns if they fail, but continues
using the full flange width for all
calculations
Use reduced width: the program does
the checks, warns if the checks fail, but
continues with a reduced bottom flange
width for stress calculations (bottom
flange width = 20% of the effective span
length for the location in question)
Exhibit 26: Box Girder Properties Form – Bottom Flange Width Applicability Checks Option.
INPUT FORMS 55
3.10 Span Information Forms
3.10.1 General
A Span Information Form is to be filled out for each span of the girder under investigation. A
sample filled-in Span Information Form for Span 1 is shown in Exhibit 27. Article 3.10.8 contains
the table describing the data to be entered in the Span Information Form.
Exhibit 27: Span Information Form.
3.10.2 Symmetrical Span Declaration
If the girder is symmetrical about the bridge centerline, the Span Information Form may be
used to declare a particular span a Symmetrical span (if desired), as shown for Span 3 in
Exhibit 28 (which is symmetrical to Span 1). A symmetrical span is a span on the right side of
the bridge centerline that is symmetrical to a span on the left side of the bridge centerline. By
declaring a span to be a symmetrical span, no further input is required for that span and the
amount of output is also reduced. For spans that are not declared to be symmetrical, the span
length must be entered on the form.
56 INPUT FORMS
Exhibit 28: Span Information Form: Declaration of a Symmetrical Span.
3.10.3 Non-Composite Uniform Dead Load
Additional input information requested on the Span Information Form (for spans that are not
declared to be symmetrical) includes the uniform component dead load acting on the non-
composite section, or DC1 load, over the entire length of the span under consideration.
INPUT FORMS 57
User Notes:
1) The uniform dead loads that are entered should be the loads assumed acting on the girder
under consideration and NOT the total load acting on the bridge cross-section. For box girders,
enter the total load assumed acting on the box under consideration and NOT the load on each
individual web.
2) DC1 loads typically include the weight of the concrete deck (including any integral wearing
surface), the weight of any tapers in the deck overhangs, the weight of the deck haunches and
any stay-in-place deck forms, and an assumed weight for the cross-frames/diaphragms and
details.
3) LRFD Simon automatically computes and includes the weight of the girder webs and flanges
and so the self-weight of the girder should NOT be included in the input non-composite
uniform dead load.
4) For square bridges and for bridges with skews less than or equal to 20 degrees from normal in
which the cross-frames are parallel to the skew, DC1 loads are best computed by dividing the
total load acting on the bridge cross-section equally to all the girders in the cross-section.
3.10.4 Hinges
LRFD Simon allows the input of one hinge per span. The hinge location measured from the left
end of the span is entered on the Span Information Form. If a hinge is specified, the user
should consult Articles 3.10.8 and 5.3.11 for further information.
3.10.5 Non-Composite Partial Uniform Dead Load
Partial-length uniform component dead loads acting on the non-composite steel section may
also be optionally entered on this form (Exhibit 29). Such loads may be used to input the
weight of bottom-flange tee stiffeners on box girder bottom flanges or web longitudinal
stiffeners that may be present only over a portion of the span, or the weight of any utility loads
or other loads applied to the non-composite section over only a portion of the span. Refer to
Article 3.10.8 for additional information on the input parameters A1, A2, X1 and X2 shown in
Exhibit 29.
58 INPUT FORMS
X2
X1
X1 < X2
A2
A1
Span Length
Exhibit 29: Partial-Length Uniform Non-Composite Component Dead Loads.
3.10.6 Bottom Flange Cross-Frame Spacing
Also entered on the Span Information Form is the bottom flange cross-frame spacing adjacent
to the interior piers in the span, which is used to check for lateral-torsional buckling (Article
5.3.10) of the discretely braced I-girder bottom compression flange in regions subject to
negative bending under the DC1 loads for constructibility, and under the total factored loads at
the strength limit state. For simple spans and for box-girder design, this parameter is not used
and may be left blank. Local buckling of this flange will also be checked at the strength limit
state where the flange is subject to compression.
INPUT FORMS 59
3.10.7 Top Flange Cross-Frame Spacing
A drop-down box is also provided to indicate whether or not the top flange is fully
(continuously) braced for the non-composite DC1 dead loads and the construction lateral
moment. If the answer is ″Yes″, the top flange is considered to be continuously braced for the
DC1 loads and the construction lateral moment. If the answer is ″No″, a top-flange cross-frame
spacing must be entered to allow LRFD Simon to check the discretely braced top compression
flange of the non-composite steel girder for lateral-torsional buckling (Article 5.3.10) in regions
subject to positive bending under the DC1 loads and construction lateral moment (for
constructibility and the deck pours). Local buckling of the flange will also be checked in this
case where the flange is subject to compression.
A separate drop-down box is also provided on this form to indicate whether or not the top
flange is considered fully (continuously) braced for the total factored loads at the final (i.e.
strength limit) state. If the answer is ″Yes″, the top flange is considered to be continuously
braced at the strength limit state. If the answer is ″No″, a top-flange cross-frame spacing must
be entered to allow LRFD Simon to check the discretely braced top compression flange of the
girder for lateral-torsional buckling (Article 5.3.10) under the total factored loads acting on the
non-composite section at the strength limit state in regions subject to positive bending. Local
buckling of the flange will also be checked in this case where the flange is subject to
compression.
User Note: LRFD Simon allows the user to enter a single cross frame spacing for the bottom flange
for each span, and two spacings for the top flange for each span (one for use during the
constructibility checks, and the other for use during the design checks for the final state if the top
flange is not considered to be continuously braced). For the computation of the lateral-torsional
buckling resistance of a discretely braced compression flange, the user-input value of the cross-
frame spacing, Lb, is always used. If the user-input value of the cross-frame spacing does not divide
a span into a whole number of uniform unbraced lengths, then certain calculations that depend on
the exact locations of the cross-frames cannot be done. In such cases, LRFD Simon will also
compute a uniform unbraced length for that flange that divides the entire span evenly from the
following equation:
A message is output on the first design cycle giving this computed unbraced length for the bottom
and/or top flange, which is then used in the computation of the moment gradient modifier, Cb, and
to determine whether or not the section is to be considered prismatic or nonprismatic in the
calculation of the lateral-torsional buckling resistance (Article 6.10.8.2.3 – see also Article 5.3.10).
60 INPUT FORMS
3.10.8 Span Information Form Data
Lower Upper
Choose the symmetrical span option.
Options:
Yes: if this span is symmetrical to a span
on the left side of the bridge
Symmetrical span N
centerline (no further input is
required for this span)
No: if this span is not symmetrical to a
span on the left side of the bridge
centerline
For a span that has not been declared
Span length, ft 1 ft 500 ft symmetrical, enter the length of the span under
consideration
Enter the hinge location measured from the left
end of the current span (if the current span
contains a hinge). Leave blank if there is not a
hinge in the current span.
A hinge may be specified in the span under

consideration with the following restrictions:
Hinge location, ft 1 ft 500 ft
a. One hinge is permitted per span.
b. A hinged span must have at least one adjacent
span without a hinge.
c. The user must ensure that an input structure is
stable and be aware that an unstable structure
may still generate a design.
d. See also Article 5.3.11.
Enter the uniform component dead load (DC1

load) in the span under consideration acting on
the non-composite steel section over the entire
Non-composite
-10000 10000 span length (see the related User Notes given
uniform dead load,
lb/ft lb/ft above).
lb/ft
If this is a declared symmetrical span, enter 0. or
leave blank.
INPUT FORMS 61
Lower Upper
Enter any partial uniform component dead load
(DC1 load) acting on the non-composite steel
section, A1, acting over the distance, X1, measured
Non-composite from the left end of the span under consideration
-10000 10000
partial dead load, (Exhibit 29).
lb/ft lb/ft
A1, lb/ft
If a partial uniform load is not to be entered or if
this is a declared symmetrical span, enter 0. for A1
and X1 or leave both values blank.
Enter the distance, X1, to the end of the A1 load
Distance, X1, to end measured from the left end of the span under
0 ft 500 ft
of A1 load, ft consideration (Exhibit 29). Note that X1 must be
less than X2.
Enter any partial uniform component dead load
(DC1 load) acting on the non-composite steel
section, A2, acting from the distance, X2, measured
from the left end of the span under consideration
Non-composite
-10000 10000 to the right end of the span (Exhibit 29). A2 must
partial dead load,
lb/ft lb/ft end at the right end of the span.
A2, lb/ft
If a partial uniform load is not to be entered or if
this is a declared symmetrical span, enter 0. for A2
and X2 or leave both values blank.
Enter the distance, X2, to the beginning of the A2
Distance, X2, to
load measured from the left end of the span
beginning of A2 0 ft 500 ft
under consideration (Exhibit 29). Note that X1
load, ft
must be less than X2.
Enter the bottom flange cross-frame spacing
adjacent to the interior piers in the span, which is
used to check for lateral-torsional buckling of the
discretely braced I-girder bottom compression
flange in regions subject to negative bending
Bottom flange cross
0 ft 50 ft 25 ft under the DC1 loads for constructibility, and under
frame spacing, ft
the total factored loads at the strength limit state
(see also the related User Note given above and
Article 5.3.10). May be left blank for simple spans
and for box-girder designs, or if this is a declared
symmetrical span.
62 INPUT FORMS
Lower Upper
Choose whether or not the top flange is
considered fully (continuously) braced for all DC1
dead load and the construction lateral moment
acting on the non-composite section.
Options:
Yes: if the top flange is considered fully
(continuously) braced for all DC1
Top flange fully
dead loads and the construction
braced for non- No
lateral moment acting on the non-
composite loads
composite section.
No: if the top flange is considered to be
discretely braced for all DC1 dead
loads and the construction lateral
moment acting on the non-
composite section, and enter the
next input item.
If No is chosen for the preceding option, enter a

top-flange cross-frame spacing to be used to
check the discretely braced top compression
flange of the non-composite steel girder for
lateral-torsional buckling in regions subject to
positive bending under the DC1 loads and
construction lateral moment (for constructibility
Non-composite top
and the deck pours). See also the related User
flange cross frame 0 ft 50 ft 25 ft
Note given above and Article 5.3.10.
spacing, ft
If Yes is chosen for the preceding option to
indicate that the top flange is considered fully
(continuously) braced for the DC1 loads and
construction lateral moment, or if this is a
declared symmetrical span, this input value is
ignored.
INPUT FORMS 63
Lower Upper
Choose whether or not the top flange is
considered fully (continuously) braced for the
total factored loads at the strength limit state.
Options:
Yes: if the top flange is considered fully
Top flange fully (continuously) braced for the total
braced for final No factored loads at the strength limit
state state
No: if the top flange is considered to be
discretely braced for the total
factored loads acting on the non-
composite section at the strength
limit state, and enter the next input
item.
If No is chosen for the preceding option, enter a
top-flange cross-frame spacing to be used to
check the discretely braced top compression
flange of the non-composite steel girder for
lateral-torsional buckling in regions subject to
positive bending under the total factored loads at
Final state top
the strength limit state. See also the related User
flange cross frame 0 ft 50 ft 25 ft
Note given above and Article 5.3.10.
spacing, ft
If Yes is chosen for the preceding option to
indicate that the top flange is considered fully
(continuously) braced for the total factored loads
at the strength limit state, or if this is a declared
symmetrical span, this input value is ignored.
64 INPUT FORMS
Lower Upper
Enter (optionally) the total unfactored flange
lateral moment due to the deck overhang loads
(and any other effects) to be considered in the
constructibility design checks at all sections that
are in positive bending under the non-composite
loads in the span under consideration, including
the checks for the deck pours (if deck pours are
specified on the Deck Pour Cross Section
Information Form – Article 3.11.7). The lateral
moment is applied to the top and bottom flanges
of the non-composite steel girder, and is
considered in the nominal yielding, local buckling,
and lateral-torsional buckling checks for
construction and the deck pours using the one-
third rule equations (AASHTO LRFD Articles
6.10.3.2.1 and 6.10.3.2.2). The factored lateral
bending stress in each flange (including any
Construction lateral amplification – see below) is limited to 0.6Fy, as
0 kip-ft 300 kip-ft 0 kip-ft
moment, kip-ft specified in AASHTO LRFD Article 6.10.1.6.
LRFD Simon amplifies the top (compression)

flange lateral bending stress, as required
according to the provisions of AASHTO LRFD
Article 6.10.1.6 (see Eqs. 6.10.1.6-2 and 6.10.1.6-
4) prior to making the design checks. For lateral-
torsional buckling checks, the amplification factor
is computed at each end and at the mid-point of
the unbraced length, and the largest value is used
at all sections within the unbraced length. For
nominal yielding and local buckling checks, the
amplification factor is computed at the section
under consideration. The bottom (tension) flange
lateral bending stress is not amplified.
This value is typically only entered for an exterior

girder.
INPUT FORMS 65
3.11 Cross Section Information Forms
3.11.1 General
Cross Section Information Forms are to be filled out for each span of the girder under
investigation that has not previously been declared a symmetrical span on the Span
Information Form. These forms are used to input a girder to be evaluated when the LRFD
Analysis run option (Article 5.1.1) is chosen, or to input a starting design for the girder when the
LRFD Design run option (Article 5.1.2) is chosen.
For each span that has not been declared to be a symmetrical span, a Cross Section Information
Form must be filled out for the web, the top flange, the bottom flange and the deck slab. The
first column on each of these forms is used to define a range or an End Location, which is the
distance from the left end of the span to the right end of the web, top flange, bottom flange or
slab section entered on that particular line. An End Location must be entered on each line in a
data set. Design checks are generated at each defined End Location. For the web and flanges,
the difference between two successive End Location distances defines the length of the web or
flange plate in that particular section. The End Location entered on the first line for each data
set must be greater than zero. The End Location entered on the last line for each data set must
precisely equal the length of the span under consideration. If only one line is entered for a
particular data set, the End Location entered on that line must equal the length of the span.
The ranges defined by each End Location should preferably be made larger than 1/20th of the
span length, and section changes should also preferably not be located at a span 20th point.
This will help to avoid the potential for a slight asymmetry in the analysis results should a
symmetrical girder not be declared symmetrical on the Span Information Form (Article 3.10). If
this should occur, the design should not be significantly affected. Cross Section Information
Forms must be filled out to locate the field splices in each span measured from the left end of
the span, and to optionally define the deck pours.
If flange plate sizes are not entered, they will default to internal values that are a function of
the input vertical web depth. Omission of a flange is not permitted and flanges are assumed to
be continuous across interior supports. When the LRFD Design run option is chosen (Article
5.1.2), the program attempts to maintain cross-section continuity over a support, but since the
design moves from left to right, it is possible (but unlikely) that a discontinuity in flange
geometry could result at an interior support. The user should scan the design to confirm that
such continuity exists.
The Cross Section Information Forms for each data set are discussed in more detail below.
66 INPUT FORMS
3.11.2 Web Cross Section Information Form
3.11.2.1 General
The Web Cross Section Information Form is used to define the vertical web depth (constant or
varying), the web plate specified minimum yield stress (Fy), the web plate thickness, and various
web-stiffener parameters over each defined range within the span under consideration. A
partial sample filled-in Web Cross Section Information Form for the web in Span 1 is shown in
Exhibit 30. The complete form is shown in Exhibit 31. Article 3.11.2.4 contains the table
describing the data to be entered in the Web Cross Section Information Form. The form is
accessed by clicking on the Web tab at the top of the form. Up to 10 web ranges may be
entered per span.
Exhibit 30: Web Cross Section Information Form (Partial) – Span 1.
INPUT FORMS 67
Exhibit 31: Web Cross Section Information Form (Complete) – Span 1.
3.11.2.2 Web Depth, Thickness &Yield Stress
The vertical web depth is to be entered at the left end and right end of a particular section or
range. This allows the user to enter a varying web depth, if desired. If the vertical web depth at
the left end of the range is negative, the start of a parabolic haunch is assumed by LRFD Simon.
If two or more successive negative ranges are specified, the overall parabola will not be exact.
If the vertical web depth at the left end of the range is positive and does not equal the vertical
web depth at the right end, a linear haunch is assumed. For a linear or parabolic haunch, the
inclined nature of the lower-flange force is not considered in the flange stress or shear
computations. Instead, a section within a haunch is treated as if it were within a prismatic
girder of the same depth. The user is referred to AASHTO LRFD Article 6.10.1.4 for additional
information on variable web-depth members. For a box girder with a varying web depth and
sloping webs, see also Article 5.3.4.2.
68 INPUT FORMS
User Notes:
1) It is recommended that as a minimum, a range be defined to each cross-frame in

the span on the Web Cross Section Information Form. Design checks are generated
at each defined range location and this will ensure that fatigue checks are made by
LRFD Simon at each cross-frame location.
2) For a box-girder design with sloping webs, enter the vertical web depth on the Web
Cross Section Information Form. An adjustment for the web slope will be made
internally using the horizontal offset ratio entered on the Box Girder Properties
Form (Article 3.9).
3) Enter web thicknesses to the nearest 1/16 inch. Fabricators prefer a minimum web
thickness of ½ inch to reduce the deformation of the web and potential weld
defects.
Hybrid girders are defined in LRFD Simon by entering a lower yield stress for the web than the
yield stress for one or both flanges. The user must ensure that the final plate thicknesses are
available with the designated yield stress. For hybrid girders, the computed hybrid factor, Rh,
specified in AASHTO LRFD Article 6.10.1.10.1 is calculated and appropriately applied by LRFD
Simon to account for the non-linear variation of bending stresses caused by the yielding of the
lower-strength steel in the web (for a homogeneous girder, Rh is equal to 1.0). Rh is not applied
in fatigue computations. The value of Rh computed by LRFD Simon is output in the Detailed
Information Table at each section that is checked.
3.11.2.3 Web Stiffener Parameters
3.11.2.3.1 Transversely Stiffened Check Box
If a particular section of the web is, or is anticipated to be, transversely stiffened, check the
Transversely stiffened box on the Web Cross Section Information Form (Exhibit 31). The need
for transverse stiffeners and actual transverse stiffener spacings are determined later on by
LRFD Simon after a successful design has been detected (see Article 5.3.6.2). As a result, the
user is advised that shear will be checked in the specified web section during the design cycles
assuming that the section is either transversely stiffened or unstiffened depending on whether
or not the Transversely stiffened box is checked for that section. If during the stiffener design,
LRFD Simon determines that transverse stiffeners are or are not required within one or more
sections (that is, opposite to what was selected for those sections), the user should re-evaluate
the final girder for one design cycle using the LRFD Analysis run option (Article 5.1.1) with the
checkmarks added or removed within those sections, as applicable, and with the maximum
stiffener spacings within each stiffened web section input in order to properly re-evaluate the
girder for shear (see below).
INPUT FORMS 69
3.11.2.3.2 Minimum Transverse Stiffener Spacing
Because the actual transverse stiffener spacings are not determined by LRFD Simon until after a
successful design has been detected, the actual transverse stiffener spacings are not yet known
during the design routines. Thus, the user-input Minimum transverse stiffener spacing on the
Web Cross Section Information Form (Exhibit 31) is used by the design routines in the
computation of the constant C in the web shear resistance equations. The values that should be
input for the minimum transverse stiffener spacing are dependent on whether the LRFD
Analysis or LRFD Design run option is chosen on the General Properties Form (Article 3.2), as
follows:
3.11.2.3.2.1 LRFD Analysis Run Option
When the LRFD Analysis run option (Article 5.1.1) is selected to evaluate an existing girder for
one design cycle and the actual transverse stiffener spacing is known (either from an existing
design or from a preceding run using the LRFD Design option), the user-input ‘Minimum
transverse stiffener spacing’ should be set equal to the actual maximum transverse stiffener
spacing within the transversely stiffened web section under consideration. The ‘Transversely
stiffened’ box for that section should also be checked. If there are no transverse stiffeners
within the web section under consideration, leave the box unchecked and the minimum
transverse stiffener spacing blank. In addition, at end panels, a separate web section should be
defined with a length equal to the spacing from the end support to the first transverse stiffener
in the end panel, and the ‘Minimum transverse stiffener spacing’ for that section should be set
equal to that spacing. These steps will ensure that the girder is properly evaluated for shear by
the design routines, and should probably be considered after a final design is obtained using
LRFD Simon to ensure that the proper performance ratios for shear are output in the final
design report. Note that the column marked Reduce web thickness on the Web Cross Section
Information Form (Exhibit 31) has no effect when the LRFD Analysis run option is chosen.
3.11.2.3.2.2 LRFD Design Run Option
When the LRFD Design run option is chosen (Article 5.1.2), the user-input Minimum transverse
stiffener spacing is used to compute a large web shear resistance during the web design so that
the thinnest web possible is selected. The default if no value is entered by the user is one-half
the vertical web depth at the right end of the span under consideration. When the actual
transverse stiffener spacing is then later determined for the final web that is selected, the user-
input minimum spacing is not likely to result because the minimum number of stiffeners is
selected by LRFD Simon, thus placing them at the maximum spacing.
70 INPUT FORMS
User Note: Since the constant C cannot exceed a value of 1.0, a maximum value for the
input Minimum transverse stiffener spacing (in inches) can be computed as:
where D is the web depth (in.), tw is the web thickness (in.) and Fyw is the web yield
stress (ksi). A value of do smaller than that given by this equation will not increase the
web shear resistance. Thus, it is recommended that this value be used for the user-
input ‘Minimum transverse stiffener spacing’ in transversely stiffened sections (in lieu of
the default value) whenever the LRFD Design run option is chosen and the ‘Reduce web
thickness’ box is checked.
If the box in the column marked Reduce web thickness on the Web Cross Section Information
Form (Exhibit 31) is checked, and the LRFD Design run option is selected, LRFD Simon will
attempt to make the trial web as thin as permitted by AASHTO. If it is desired that the initial
trial web thickness in a set of transversely-stiffened web sections not be reduced during the
web design, this box should not be checked in that set of sections; this may result in the design
of a partially stiffened web section with transverse stiffeners located only in the vicinity of the
supports, which is often a cost-effective solution.
User Note: A helpful guideline is that approximately 10 pounds

of web material should be saved for every pound of stiffener
material added.
INPUT FORMS 71
3.11.2.4 Web Cross Section Information Form Data
Lower Upper
Enter the distance from the left end of the span to
the right end of the web section.
The distance entered for the first range in each set

of cross section categories must be greater than
zero. The distance entered for the last range in
each set of cross section categories must precisely
End location, ft 0 ft 500 ft
equal the span length. Up to 10 web ranges may
be entered per span.
Ranges should preferably be made larger than a

20th of the span length. Section changes should
also preferably not be located at a span 20th
point.
Enter the web depth at the left end of the web
section.
Input this value as negative if this is the start of a

parabolic haunch. If two or more consecutive
Vertical web depth 12 in 288 in
negative ranges are specified, the overall parabola
left, in -288 in -12 in
is not exact. For box girders with a varying web
depth and sloping webs, see Article 5.3.4.2.
For box girder design, enter the vertical web

depth.
Enter the web depth at the right end of the web
section.
If the vertical web depth left is positive and does

Vertical web depth
12 in 288 in not equal the vertical web depth right, a linear
right, in
haunch is assumed.
For box girder design, enter the vertical web

depth.
Enter the minimum specified yield strength of the
web in the web section.
Web Fy, ksi 18 ksi 140 ksi 50 ksi
Enter a web yield strength less than the yield
strength of one or both flanges to define a hybrid
section (see Article 3.11.2.2).
72 INPUT FORMS
Lower Upper
Enter the thickness of the web in the web section.
LRFD Simon will check if the web slenderness,

D/tw, in the web section exceeds 150 and no
Web thickness, in 0.219 in 2 in longitudinal web stiffener is provided, or if a
longitudinal web stiffener is provided and D/tw
exceeds 300 (AASHTO LRFD Articles 6.10.2.1 and
6.11.2.1). D is measured along the web slope in
this check for a box girder with inclined webs.
Check this box if this web section is to be
transversely stiffened (see Article 3.11.2.3.1)
The user is advised that shear will be checked in

the specified web section during the design cycles
assuming that the section is either transversely
Transversely stiffened or unstiffened.
stiffened
If the bill-of-materials routines determine that
transverse stiffeners are or are not required in this
section (opposite to what was selected – see
Article 5.3.6.2), the girder should be reevaluated
for one design cycle with the opposite parameter
specified for this section.
See Article 5.3.6.4 for additional information on
longitudinal web stiffeners
Top web
longitudinal 2 in 24 in
Enter the width of the top web longitudinal
stiffener width, in
stiffener in the web section (leave blank if no top
web longitudinal stiffener in this section).
Top web
Enter the thickness of the top web longitudinal
longitudinal
0.25 in 3 in stiffener in the web section (leave blank if no top
stiffener thickness,
web longitudinal stiffener in this section).
in
Bottom web Enter the width of the bottom web longitudinal
longitudinal 2 in 24 in stiffener in the web section (leave blank if no
stiffener width, in bottom web longitudinal stiffener in this section).
Bottom web Enter the thickness of the bottom web
longitudinal longitudinal stiffener in the web section (leave
0.25 in 3 in
stiffener thickness, blank if no bottom web longitudinal stiffener in
in this section).
INPUT FORMS 73
Lower Upper
Check this box to have LRFD Simon make the web
in this section as thin as permitted by AASHTO.
Uncheck this box if the trial web thickness for this
web section is not to be reduced.
Do not
Reduce web
reduce web
thickness This parameter may be used in conjunction with a
thickness
transversely stiffened web when the user desires
a partially stiffened web (see Article 3.11.2.3.2).
Enter a minimum transverse stiffener spacing,

which is used in the design routines to compute
the constant C in the shear capacity equations
(see Article 3.11.2.3.2).
One half of
the input During the web design, this minimum transverse
Minimum vertical web stiffener spacing is used so that the thinnest web
transverse stiffener 3 in 864 in depth at the possible is selected (see Article 3.11.2.3.2).
spacing, in right end of
the current During the subsequent transverse stiffener
span. spacing design in the bill-of-materials routines
(Article 5.3.6.2), this minimum spacing may not
result because the minimum number of transverse
stiffeners is selected thus placing them at the
maximum spacing.
3.11.3 Top Flange Cross Section Information Form
3.11.3.1 General
The Top Flange Cross Section Information Form is used to define the top flange plate width, top
flange plate thickness, top flange plate specified minimum yield stress (Fy) and top flange plate
specified minimum ultimate tensile stress (Fu) over each defined range within the span under
consideration. A sample filled-in Top Flange Cross Section Information Form for the top flange
in Span 1 is shown in Exhibit 32. Article 3.11.3.2 contains the table describing the data to be
entered in the Top Flange Cross Section Information Form. The form is accessed by clicking on
the Top Flange tab at the top of the form. Up to 10 top flange ranges may be entered per
span.
74 INPUT FORMS
Exhibit 32: Top Flange Cross Section Information Form – Span 1.
INPUT FORMS 75
3.11.3.2 Top Flange Cross Section Information Form Data
Lower Upper
Limit Limit
the right end of the top flange section.

equal the span length. Up to 10 top flange ranges
may be entered per span.

point.
Enter the width of the top flange in the section
(note that if top flange plate sizes are not entered,
they will default to internal values that are a
Top flange width, in 6 in 240 in function of the input vertical web depth).
For box girder design, the data entered here and

below will apply to both top flanges in the section.
Top flange Enter the thickness of the top flange in the
0.3125 in 4 in
thickness, in section.
Enter the minimum specified yield strength of the
Top flange Fy, ksi 18 ksi 140 ksi 50 ksi
top flange in the section.
76 INPUT FORMS
Enter the minimum specified ultimate tensile
strength of the top flange in the section (AASHTO
LRFD Table 6.4.1-1).
ASTM A709 Grade 36: Fu = 58 ksi
ASTM A709 Grades 50/50S: Fu = 65 ksi
ASTM A709 Grades 50W/HPS 50W: Fu = 70 ksi
ASTM A709 Grade HPS 70W: Fu = 85 ksi
ASTM A709 Grade HPS 100W:
t ≤2.5 in. Fu = 110 ksi
2.5 in. < t ≤ 4.0 in. Fu = 100 ksi
Top flange Fu, ksi 18 ksi 280 ksi 65 ksi
The ultimate strength of the top flange steel is
used to compute the minimum required An/Ag
ratio to satisfy AASHTO LRFD Eq. 6.10.1.8-1 when
the top flange is subject to tension at a defined
field splice location (if the splice is bolted). The
minimum required ratio is provided in
informational messages in the LRFD Simon output
at all defined field splice locations entered on the
Field Splice Cross Section Information Form
(Article 3.11.6.1).
INPUT FORMS 77
3.11.4 Bottom Flange Cross Section Information Form
3.11.4.1 General
The Bottom Flange Cross Section Information Form is used to define the bottom flange plate
width, bottom flange plate thickness, bottom flange plate specified minimum yield stress (Fy)
and bottom flange plate specified minimum tensile stress (Fu) over each defined range within
the span under consideration. A sample filled-in Bottom Flange Cross Section Information Form
for the bottom flange in Span 1 is shown in Exhibit 33. Article 3.11.4.2 contains the table
describing the data to be entered in the Bottom Flange Cross Section Information Form. The
form is accessed by clicking on the Bottom Flange tab at the top of the form. Up to 10 bottom
flange ranges may be entered per span.
Exhibit 33: Bottom Flange Cross Section Information Form – Span 1.
78 INPUT FORMS
3.11.4.2 Bottom Flange Cross Section Information Form Data
Lower Upper
Limit Limit
the right end of the bottom flange section.

equal the span length. Up to 10 bottom flange
ranges may be entered per span.

point.
Enter the width of the bottom flange in the
section (note that if bottom flange plate sizes are
not entered, they will default to internal values
that are a function of the input vertical web
Bottom flange
6 in 240 in depth).
width, in
For box girder design, enter the full bottom flange
width in the section (including the bottom flange
width outside the webs).
Bottom flange Enter the thickness of the bottom flange in the
0.3125 in 4 in
thickness, in section.
Bottom flange Fy, Enter the minimum specified yield strength of the
18 ksi 140 ksi 50 ksi
ksi bottom flange in the section.
INPUT FORMS 79
Enter the minimum specified ultimate tensile
strength of the bottom flange in the section
(AASHTO LRFD Table 6.4.1-1).
ASTM A709 Grade 36: Fu = 58 ksi
ASTM A709 Grades 50/50S: Fu = 65 ksi
ASTM A709 Grades 50W/HPS 50W: Fu = 70 ksi
ASTM A709 Grade HPS 70W: Fu = 85 ksi
ASTM A709 Grade HPS 100W:
t ≤2.5 in. Fu = 110 ksi
Bottom flange Fu, 2.5 in. < t ≤ 4.0 in. Fu = 100 ksi
18 ksi 280 ksi 65 ksi
ksi The ultimate tensile strength of the bottom flange
steel used to compute the minimum required
An/Ag ratio to satisfy AASHTO LRFD Eq. 6.10.1.8-1
when the bottom flange is subject to tension at a
defined field splice location (if the splice is bolted).
The minimum required ratio is provided in
informational messages in the LRFD Simon output
at all defined field splice locations entered on the
Field Splice Cross Section Information Form
(Article 3.11.6.1).
80 INPUT FORMS
3.11.5 Slab Cross Section Information Form
3.11.5.1 General
The Slab Cross Section Information Form is used to define the effective composite deck slab
width, effective composite deck slab thickness, and the area of the longitudinal reinforcement
within the deck slab. A sample filled-in Slab Cross Section Information Form for Span 1 is shown
in Exhibit 34. Article 3.11.5.2 contains the table describing the data to be entered in the Slab
Cross Section Information Form. The form is accessed by clicking on the Slab tab at the top of
the form. Up to three slab ranges may be entered per span.
Exhibit 34: Slab Cross Section Information Form – Span 1.
INPUT FORMS 81
3.11.5.2 Slab Cross Section Information Form Data
Lower Upper
the right end of the slab section.

equal the span length. Up to three slab ranges
may be entered per span.

point.
Enter the effective composite slab width
associated with the girder under consideration in
the slab section. The user should ensure that the
input width does not exceed the girder spacing.
This input value is used in calculating the

composite section properties used to compute
stresses and section capacities with the specified
section only when the moment in that section is
positive. The effective composite slab width is also
used to compute the moments of inertia within
the specified section for use in the stiffness
analysis regardless of the sign of the moment. If
Effective composite
0 in 600 in 0. is entered, only the stiffness of the steel girder
slab width, in
is considered in the analysis within that section
(Not recommended unless entire girder is non-
composite). If a value greater than 0. is entered
anywhere in a span, the stud shear connectors are
assumed to be effective over the full length of the
span (except for the optional interruption of studs
permitted for I-girders over interior supports – see
Articles 3.8.2 and 5.3.7).
For box girder design, enter the effective

composite slab width associated with the full tub
girder, and not the effective composite slab width
associated with a single web.
82 INPUT FORMS
Lower Upper
Enter the effective composite slab thickness
associated with the girder under consideration in
Effective composite the slab section. The thickness entered should be
0 in 24 in
slab thickness, in the structural slab thickness (i.e. total slab
thickness minus the thickness of any integral
wearing surface).
Enter the area of the longitudinal reinforcing steel
in the slab section (enter “0” or leave blank if the
longitudinal reinforcing steel is not to be
considered).
This area is included in calculating the section

properties used to compute stresses and section
capacities within the specified section only when
the moment in that section is negative. The input
reinforcing steel area is assumed placed in a single
layer in the concrete deck at the centroidal
location entered on the General Properties Form
(Article 3.2).
Reinforcement
0 in 60 in
area, A's, in2 This area is not included in calculating the
moments of inertia within that section for use in
the stiffness analysis.
To include the only the rebar along with the steel

girder in the stiffness analysis within the specified
section, enter an effective composite slab width in
that section equal to (n x Ars)/t,, where t, is the
effective composite slab thickness entered for
that section and n is the modular ratio (Not
recommended).
For box girder design, enter the rebar area in the

slab section for the full box.
3.11.6 Field Splice Cross Section Information Form
3.11.6.1 General
The Field Splice Cross Section Information Form is used to define the distance from the left end
of a span to one or more field splices within that span. Up to three field splices per span may
be entered. An input consistency warning is generated if the user enters a field splice location
within 5 percent of the span length from a support.
INPUT FORMS 83
At each defined field splice location, LRFD Simon assumes there are holes in the tension flange
to accommodate a bolted field splice and checks the factored tensile stress on the gross area of
the flange, ft, against the specified minimum yield strength of the flange, Fy. This check is made
for the construction load case, for the deck pours, for the Strength I load case for dead load
plus positive live load moment, and for the Strength I load case for dead load plus negative live
load moment in that order. In LRFD Design mode, the flange will be resized if any of these
checks fail. Informational messages are also provided at each defined field splice location
advising the user that LRFD Simon does not check ft against the value, 0.84(An/Ag)Fu (refer to
AASHTO LRFD Eq. 6.10.1.8-1). The messages further indicate the value of (ft/0.84 * Fu) that the
ratio of (An/Ag) must exceed in the tension flange at the splice in order to satisfy AASHTO LRFD
Eq. 6.10.1.8-1. A separate value is again provided for the construction load case, for the deck
pours, for the Strength I load case for dead load plus positive live load moment, and for the
Strength I load case for dead load plus negative live load moment in that order.
Also provided in the results at each defined field splice location is field splice design information
to assist the user with the entering of the necessary data into the separate NSBA Splice design
spreadsheet (for additional information on NSBA Splice, please visit the NSBA homepage at
www.steelbridges.org) for the design of the bolted field splice at each location (Article 5.3.8).
The information is provided once an acceptable design has been detected by LRFD Simon.
A sample filled-in Field Splice Cross Section Information Form for the field splice in Span 1 is
shown in Exhibit 35. Article 3.11.6.2 contains the table describing the data to be entered in the
Field Splice Cross Section Information Form. The form is accessed by clicking on the Field
Splice tab at the top of the form.
84 INPUT FORMS
Exhibit 35: Field Splice Cross Section Information Form.
INPUT FORMS 85
3.11.6.2 Field Splice Cross Section Information Form Data
Lower Upper
a field splice. An input consistency warning is
Field splice location generated if the user enters a field splice
from the left end of 0 ft 500 ft location within 5 percent of the span length
the span, ft from a support.
Up to three splices per span can be entered.
86 INPUT FORMS
3.11.7 Deck Pour Cross Section Information Form
3.11.7.1 General
The Deck Pour Cross Section Information Form is used to optionally define the sequential deck
pours in each span. Article 3.11.7.2 contains the table describing the data to be entered in the
Deck Pour Cross Section Information Form. The form is accessed by clicking on the Deck Pours
tab at the top of the form. Up to five pour ranges per span may be entered.
A sample filled-in Deck Pour Cross Section Information Form for Span 1 (the leftmost span) for
the sequential deck pour sequence shown in Exhibit 36 is shown in Exhibit 37. The Deck Pour
Cross Section Information Form for Span 2 (the center span) is shown in Exhibit 38. Since Span
3 (the rightmost span) has previously been declared to be symmetrical to Span 1, a Deck Pour
Cross Section Information Form for Span 3 need not be completed; Pour 1 is automatically
reflected to Span 3. Should it desired to have a separate pour in Span 3, then Span 3 should
not be declared symmetrical to Span 1.
Accumulated factored stresses in the steel girder due to the deck pours are calculated using the
properties of the steel section only. Deck stresses due to the deck pours are currently not
accumulated.
Exhibit 36: Sample Sequential Deck Pour Sequence.
INPUT FORMS 87
Exhibit 37: Deck Pour Cross Section Information Form – Span 1.
Exhibit 38: Deck Pour Cross Section Information Form – Span 2.
88 INPUT FORMS
3.11.7.2 Deck Pour Cross Section Information Form Data
Lower Upper
Indicate which deck pour is being described. The
user can enter up to five pour ranges per span.
With a maximum of 12 spans allowed, this gives
up to 60 pours total.
Pour number 1 60
All pours with the same number are analyzed at
the same time; i.e., if Pour number 1 is defined in
both Spans 1 and 5, both pours will be considered
to be cast at the same time.
Enter the distance from the left end of the span
under consideration to the start of the deck pour
Pour start location,
0 ft 500 ft under consideration. The pour start and end
ft
locations must be different; the pour start location
must be less than the pour end location.
Enter the distance from the left end of the span
under consideration to the end of the deck pour
under consideration.
Pour end location,
0 ft 500 ft
ft The program will check to ensure that the deck
pours do not overlap. The user should ensure that
the entire length of the girder is covered with the
input deck pours.
INPUT FORMS 89
3.12 Cost Forms
3.12.1 General
A Material Unit Cost Form and a Fabrication Cost Factor Form may be optionally filled out by
the user. The data entered on these forms are used by LRFD Simon to calculate cost indicators
for the girder, which are listed by span and by component in the Bill of Materials. A user may
wish to use the factors to evaluate the relative cost effects of utilizing a thicker web in lieu of
providing transverse stiffeners. Because a user may wish to use these factors to compare
designs for I and box girders for the same bridge, and because the two types of designs may use
a different number of girders, the cost is computed as the cost per girder times the number of
girders.
3.12.2 Material Unit Cost Form
3.12.2.1 General
The Material Unit Cost Form is used to enter steel costs per ton for various yield strengths. A
sample filled-in Material Unit Cost Form is shown in Exhibit 39. The costs shown in the exhibit
are for illustration only and do not necessarily represent present-day costs for steel. The user is
advised to consult with the NSBA regarding these costs. Article 3.12.2.2 contains the table
describing the data to be entered in the Material Unit Cost Form. If fabrication cost factors are
also entered on the Fabrication Cost Factor form (see Article 3.12.3), the factors are multiplied
by the appropriate material unit costs entered here to obtain total cost indicators that reflect
the cost of fabrication.
90 INPUT FORMS
Exhibit 39: Material Unit Cost Form.
INPUT FORMS 91
3.12.2.2 Material Unit Cost Form Data
Lower Upper
Material unit cost, Enter a material unit cost factor (per ton) for 36
$0/ton $600 / ton
36 ksi steel, $/ton ksi steel (optional).
$0/ton $600 / ton
$0/ton $600 / ton
$0/ton $600 / ton
Material unit cost, Enter a material unit cost factor (per ton) for 90-
90 - 100 ksi steel, $0/ton $600 / ton 100 ksi steel (optional).
$/ton
3.12.3 Fabrication Cost Factor Form
3.12.3.1 General
The Fabrication Cost Factor Form is used to enter relative cost factors (or multipliers) that
reflect the relative cost of fabrication for different fabricated girder components. Separate
factors may be entered for the webs, flanges, web and bottom-flange longitudinal stiffeners,
and transverse and bearing stiffeners. A sample filled-in Fabrication Cost Factor Form is shown
in Exhibit 40. The cost factors shown in the exhibit are for illustration only and do not
necessarily represent relative present-day costs for fabrication. The user is advised to consult
with the NSBA regarding these cost factors. Article 3.12.3.2 contains the table describing the
data to be entered in the Fabrication Cost Factor Form. If material unit costs are also entered
on the Material Unit Cost form (see Article 3.12.2), the factors entered here are multiplied by
the appropriate material unit costs to obtain total cost indicators that reflect the cost of
fabrication. For box girders, it is recommended that cost factors be entered to assist in arriving
at an efficient design for the bottom compression flange (see Article 5.3.4.2).
92 INPUT FORMS
Exhibit 40: Fabrication Cost Factor Form.
INPUT FORMS 93
3.12.3.2 Fabrication Cost Factor Form Data
Lower Upper
Fabrication cost Enter a fabrication cost factor for the webs
0.0 1.0
factor, webs (optional).
Fabrication cost Enter a fabrication cost factor for the flanges
0.0 1.0
factor, flanges (optional).
Fabrication cost
factor, web Enter a fabrication cost factor for the web
0.0 1.0
longitudinal longitudinal stiffeners (optional).
stiffeners
Fabrication cost
factor, transverse Enter a fabrication cost factor for the transverse
0.0 1.0
and bearing and bearing stiffeners (optional).
stiffeners
Fabrication cost
factor, flange Enter a fabrication cost factor for the flange
0.0 1.0
longitudinal longitudinal stiffeners (optional).
stiffeners
94 INPUT FORMS
3.13 Web Depth Optimization
3.13.1 General
The Web Depth Optimization Form is used to instruct LRFD Simon to perform a web depth
optimization. The web depth optimization function assists the user with optimization of the
vertical web depth of an I- or Box Girder. LRFD Simon automatically generates a series of trial-
design input files for the LRFD Simon engine from an acceptable starting design input file. The
generated input files differ from the starting input only in the vertical web depth. Each of these
input files is processed automatically by the analysis engine, and a table is prepared listing the
depth, weight, and cost (based on user-input cost factors – see Article 3.12) for the depths that
have acceptable designs.
The user may specify a web depth optimization when either the LRFD Design or LRFD Analysis
run option is chosen on the General Properties Form (Article 3.2). However, if the LRFD
Analysis run option is chosen, the same size flanges will be used for all runs, which will probably
not result in the most efficient designs. Further information on the web depth optimization
procedure is provided in Article 5.3.5.
A sample filled-in Web Depth Optimization Form is shown in Exhibit 41. Article 3.13.2 contains
the table describing the data to be entered in the Web Depth Optimization Form.
INPUT FORMS 95
Exhibit 41: Web Depth Optimization Form.
96 INPUT FORMS
3.13.2 Web Depth Optimization Form Data
Lower Upper
Choose whether or not to have LRFD Simon
perform a web depth optimization (see Article
5.3.5).
Options:
Web optimization Yes
No
If Yes is chosen, a web depth optimization will be

done, meaning that several input files will be
created and run based on the input criteria below.
Number of Enter the number of increments that the web
variations below 0 5 depth will be decreased below the starting web
start depth.
Number of Enter the number of increments that the web
variations above 0 5 depth will be increased above the starting web
start depth.
Choose the web depth variation type – Exhibit 42.
Options:
Fixed
Percentage
If Fixed is chosen, the web depth will be

Depth variation
decreased/increased in increments of inches from
type
the starting web depth (using the user-input
depth increment – see below).
If Percentage is chosen, the web depth will be

decreased/increased in increments that are a
percentage of the starting web depth (using the
user-input depth increment – Exhibit 42).
The amount to decrease or increase the web
Depth increment, depth below or above the starting web depth at
0 100
in. or % each increment based on the depth variation type
that is selected.
INPUT FORMS 97
Exhibit 42: Web Depth Optimization Form – Depth Variation Type Option.
98 INPUT FORMS
3.14 Result Controls
3.14.1 General
The Result Controls Form is used to help control the amount of output that is generated by
LRFD Simon. A sample filled-in Result Controls Form is shown in Exhibit 43. Article 3.14.2
contains the table describing the data to be entered in the Result Controls Form.
Exhibit 43: Result Controls Form.
INPUT FORMS 99
3.14.2 Result Controls Form Data
Upper
Input Item Lower Limit Limit Default Remarks
Choose the frequency of cycles after which results
are printed.
Options:
Number: Cycle frequency of printed
output (e.g. enter ‘1’ for every
Frequency of
cycle, ‘2’ for every other cycle
cycles after First and
-1 starting with Cycle 2, etc.)
which results last only
Blank: First and last cycles only
are printed
(Default)
-1: Last cycle only
The user is advised that if -1 is selected for this

parameter, any messages output during the first
design cycle will be missed.
Performance
ratio above
Enter the performance ratio above which
which 0.0 2.0 0.50
messages are output.
messages are
output
Choose whether or not detailed stresses and
section properties are to be printed.
Options:
Print details No
Yes: if detailed stresses and section
properties are to be printed
No: if detailed stresses and section
properties are not to be printed
100 INPUT FORMS

4 RESULTS
4.1 General
When a design or analysis is successfully completed in LRFD Simon, the results file is formatted
as XML (Exhibit 44). XML files are an open file protocol supported by most word-processing and
spreadsheet programs. As a result, LRFD Simon results files can be viewed not only within the
LRFD Simon user interface, but also within any application that supports XML (e.g. Microsoft
Excel).
Exhibit 44: Example LRFD Simon Results Formatted as XML.
An XML results file is considered “human readable” and with some effort a user could decipher
portions of the results by simple inspection using a desktop program like Microsoft Notepad.
However, the XML results files can be transformed into a more familiar format that includes
navigable bookmark links, section headings, summary tables and colorization. This is
accomplished using an Extensible Stylesheet Language (XSL) file which will parse the XML file
re-stylize it. This can be seen whenever a LRFD Simon analysis or design is successfully run and
the re-stylized XML results are displayed in the Input/Output Window Pane (Exhibit 45).
RESULTS 101
Exhibit 45: Re-stylized Results File Viewed within LRFD Simon Input/Output Window Pane.
4.2 Re-Stylized Output
LRFD Simon is delivered with a default XSL file, “Simon_output.xsl”. If you look at the XML file
shown in Exhibit 44, you can see this XSL file referenced in the second line of the results file.
Each time LRFD Simon successfully executes an analysis or design, the delivered XSL file is
copied from the program folder to the same location as the new results file.
A user has the option to customize the delivered XSL file or replace it entirely with something
that re-stylizes the results in a manner more fitting their needs. For example, a simple change
might be to embed a company logo in the results file.
4.3 User Manipulation of Results
Users may have the need to manipulate the results output by LRFD Simon. Rather than re-
entering values and risking error, LRFD Simon results files can be viewed and manipulated
directly within any application that supports XML. This section will focus specifically on the use
of Microsoft Excel; however the process is similar for many desktop applications that support
XML.
User Note: Each time and analysis or design is run in LRFD Simon, the results file is
recreated and the old one if overwritten.
102 RESULTS
An LRFD Simon results file can be opened in Excel using the standard File>Open menu as shown
in Exhibit 46. After selecting “Open”, you will be prompted to select the file to open (Exhibit
47).
Exhibit 46: Excel File Open Menu.
By default, the file type filter set within the Excel File Open dialog will cause XML files to be
displayed. However, if you are unable to see the Simon XML file, you should check the file type
filter and make sure that either “All Excel Files” or “XML Files” is selected. When selected, the
Excel File Open dialog will also show a preview of the XML file as shown in Exhibit 47.
Exhibit 47: Excel File Open Dialog with Preview.
RESULTS 103
When Excel initially reads the XML file, it will detect that an XSL Stylesheet has been associated
with the file (Exhibit 48). At this point, “Open the file with the following stylesheet applied
(select on)” should be chosen and the stylesheet “SIMON_output.xsl” selected. Upon pressing
the “OK” button, the LRFD Simon results file will open.
Exhibit 48: Import XML and Apply Stylesheet Dialog.
User Note: When an LRFD Simon XML file is opened in Microsoft Excel, the file will
open as “Read-Only” (Exhibit 49) which means that it cannot be changed. If you would
like perform an Excel operation using the results, you must first save the XML file as a
new Excel file.
Exhibit 49: LRFD Simon XML File Viewed in Excel.
In order to make use of the XML results within Excel, the file must first be saved as a native
Excel file (e.g. XLSX workbook file). This can be done by selecting “File>Save-As” from the Excel
menu and then choosing “Excel Workbook” as the file type in the “Save As” dialog (Exhibit 50).
Once the XML file has been saved as an Excel file, the contents of the results file can be used to
104 RESULTS
perform additional calculations. At this point, the new Excel file and LRFD Simon XML file are
no longer the same and when one is changed or updated, the other is not.
Exhibit 50: Excel Save as Dialog.
4.4 Creation of a New Model Input File from the Best Design
When the ′LRFD Design′ run option has been selected on the General Properties form (see
Article 3.2.2) and a satisfactory final design has been detected by LRFD Simon, a new model
input file with the revised web and flange plate sizes from the successful final design cycle will
automatically be created for possible subsequent investigations. The new model input file will
be placed in the same folder as the original model input file with the same name as the original
file, only with ′.BD′ (for Best Design) placed in-between the original file name and the file
extension ′.DAT′. A model dialog box will appear on the screen at the completion of a
successful design run to indicate the presence of the new ′Best Design′ file. If a satisfactory final
design cannot be obtained by LRFD Simon, a ′Best Design′ file will not be generated.
For I-girders, the run option (see Article 3.2.2) in the ‘Best Design’ file will be changed to ′LRFD
Analysis’. For box girders, the run option in the ‘Best Design’ file will remain ′LRFD Design′. All
RESULTS 105
other program input in the ‘Best Design’ file will remain unchanged (see further discussion
below).
When the user instructs LRFD Simon to perform a Web Depth Optimization (see Article 3.13), a
series of new ‘Best Design’ files will be created from the final successful design cycle for the run
with the original web depth and for all the runs with the web depth incremented above and
below the starting web depth as instructed by the user.
The web stiffener parameters on the Web Cross Section Information Forms (see Article
3.11.2.3) in the ‘Best Design’ file(s) remain unchanged from the parameters on the original
model input file(s). As a result, the transverse stiffener spacings and sizes that were arrived at
after a successful final design has been detected by LRFD Simon will not be reflected in the
‘Best Design’ file(s). This is due to the current limitation in the LRFD Simon input of not being
able to conveniently specify a mix of stiffened and unstiffened regions of the web, or regions
with different numbers and sizes of stiffeners. Also, only strength limit state checks are
considered by LRFD Simon when laying out the transverse stiffeners after a successful final
design has been detected. Therefore, the resulting stiffener spacings may not pass the
constructibility and special fatigue design shear checks in the specification without further
investigation by the user in a subsequent run using the ‘LRFD Analysis’ run option (see Article
3.11.2.3.2.1).
It is possible that the user-input web longitudinal stiffener size may be increased by LRFD Simon
during the transverse stiffener design (see Article 5.3.6.4). Should this occur, the revised web
longitudinal stiffener size is written to the ‘Best Design’ file(s). However, in some cases, LRFD
Simon may require an extremely thick web longitudinal stiffener that fails the Sanity Check for
the stiffener thickness (see Article 3.2.2). In such cases, in order to allow the program to run,
the web longitudinal stiffener thickness is limited to a maximum of 3.0 inches in the ‘Best
Design’ file(s), even if a thicker stiffener is required.
The bottom flanges in the ‘Best Design’ file(s) for box girders will always be unstiffened even if
longitudinal flange stiffeners were requested in the original input file. LRFD Simon currently
only allows the user to input a maximum number and range of sizes on the Box Girder
Properties Form (see Article 3.9) for the design of longitudinal flange stiffeners. There is
currently no means to input a mix of stiffened and unstiffened regions, or regions with different
numbers of flange stiffeners. Therefore, in cases where longitudinal flange stiffeners were
requested in the original input file, it is likely that the input design provided in the ‘Best Design’
file(s) will fail the specification checks if the user invokes the ‘LRFD Analysis’ run option.
106 RESULTS
5 PROGRAM ANALYSIS & DESIGN METHODOLOGY
5.1 General
The steps that occur during the execution of LRFD Simon are described as follows. In the first
step, a trial design -- which may be only a rough approximation of the final design and need not
satisfy specification requirements -- is prepared by the user and read into LRFD Simon by the
analysis routines. The trial design and the results of the structural analysis of this design are
stored. The next step depends on whether or not the LRFD Analysis or LRFD Design run option
has been selected by the user on the General Properties Form (Article 3.2).
5.1.1 LRFD Analysis Run Option
When the LRFD Analysis run option is selected, the program will run for only one analysis-
design cycle to evaluate the initial trial design. The design routines compare the trial design
with the requirements of the AASHTO LRFD Specification and the information is written to an
output file. If the design is satisfactory, the bill-of-materials routines compute dimensions and
locations of transverse stiffeners, dimensions of bearing stiffeners at each support, steel
weights, and cost indicators (Article 5.3.6). Finally, the shear-connector routines compute the
required number of shear connectors if that option is selected by the user (Article 5.3.7).
5.1.2 LRFD Design Run Option
When the LRFD Design run option is selected, the design routines compare the trial design with
the requirements of the AASHTO LRFD Specification and prepare and store a new trial design.
In this case, the design routines then decide whether the trial design should be improved. If an
improved design is needed, the analysis routines read the new trial design and repeat the
process. When a satisfactory final design has been detected, the bill-of-materials routines
compute dimensions and locations of transverse stiffeners, dimensions of bearing stiffeners at
each support, steel weights, and cost indicators (Article 5.3.6). Finally, the shear-connector
routines compute the required number of shear connectors if that option is selected by the
user (Article 5.3.7). Throughout the execution of LRFD Simon, information is written to an
output file so that the user can later trace the design process. The redesign process is discussed
in more detail in Article 5.3.4.
5.2 Analysis
The LRFD Simon analysis routines perform a line-girder analysis; that is, a single girder from the
bridge idealized as a one-dimensional member is analyzed with each execution of the program.
The analysis program divides each span of the girder into 20 segments of equal lengths. Cross-
sectional properties are computed from the input data; composite (steel-concrete) cross
PROGRAM ANALYSIS & DESIGN METHODOLOGY 107
sections, unsymmetrical cross sections, and both parabolic and linear haunches are permitted.
From the moments of inertia of the segments (which neglect web and flange longitudinal
stiffeners), the stiffness characteristics of each span are calculated. The weights of the web and
steel flanges are computed each design cycle and added to the input non-composite dead load
(therefore, the user need not included these weights in the input non-composite dead load).
The weights are based on the cross-section area over each range of the girder, with each range
defined by the plate transitions entered by the user. For regions of varying web depth, the
average of the web depth at each end of the range is used when calculating the cross-section
area. Since the program automatically breaks the girder up at 20th points when computing
cross section stiffness, nothing special is done when computing the stiffness of varying depth
regions. The web depth at each 20th point is used to compute the moment of inertia.
Influence lines are generated at the tenth points of each span, using 20 ordinates per span, for
both composite and non-composite cross sections. The analysis program does distinguish
between the effect of short-term and long-term loads on the concrete-slab behavior. The
stiffness for positive bending is used over the whole length of the girder in the analysis.
Using these influence lines, unfactored dead-load and maximum and minimum live-load
moments and shears are computed at the 1/20-length points of each span for the AASHTO HL-
93 design live load and the fatigue live load. A user-defined vehicle consisting of a truck with up
to 40 axles with user-input axle loads and spacings between each axle, acting with or without a
user-defined design lane load, can also be considered (Article 3.6). LRFD Simon considers the
live loading traveling in both directions. The rear axle spacing of the HL-93 design truck is varied
to determine the maximum effect. Axles that do not contribute to the extreme force effect
under consideration are neglected. The design vehicle loads and design lane loads are
positioned on the influence line to determine the extreme force effects. The dynamic load
allowance values input on the Loads form (Article 3.5) are included with the live-load
computations and are appropriately applied to the actions/effects due to the design truck or
design tandem (whichever controls), the user-defined vehicle (if included), and the fatigue live
load. The dynamic load allowance is not applied to the lane loads. The appropriate user-input
or internally computed distribution factors (Article 3.3) are also applied to the live-load effects.
A user-defined uniform pedestrian live load may also be considered as described in Article
3.5.3.
LRFD Simon uses the points of dead load contraflexure as input to determine how to apply the
two-truck loading that is also considered (along with the HL-93 loading) when determining
negative moments between points of contraflexure in continuous spans and interior-pier
reactions (AASHTO LRFD Article 3.6.1.3.1). LRFD Simon locates the points of contraflexure
based on the total noncomposite dead load applied to the girder. LRFD Simon uses 90 percent
of the effect of two design trucks (with the rear axle spacing fixed at 14 feet and the dynamic
load allowance applied) in combination with 90 percent of the effect of the design lane load in
this case. The minimum headway between the lead axle of one truck and the rear axle of the

other truck is 50 feet. Also considered by LRFD Simon is the case of 100 percent of the effect of
two design tandems (with the dynamic load allowance applied) in combination with 100
percent of the effect of the design lane load, with the tandems spaced between 26 ft and 40 ft
apart (AASHTO LRFD Article C3.6.1.3.1). The two trucks or tandems are placed in adjacent spans
to determine the maximum force effects. The appropriate user-input or internally computed
distribution factors (Article 3.3) are also applied to the governing live-load effects.
In addition, up to three uniform non-composite dead loads per span (including two partial dead
loads that may extend over only a portion of the span), and one uniform composite dead load,
one uniform utility load and one uniform future wearing surface load over the length of the
girder may be included. Again, LRFD Simon computes the weights of the web and steel flanges
internally and they should not be included in the input non-composite dead loads.
Also computed by LRFD Simon is the maximum live-load deflection in each span. Live load
deflections are computed using the special live loading for deflection specified in AASHTO LRFD
Article 3.6.1.3.2, and the live load distribution factor given in Article 3.3.1 assuming a uniform
distribution of the load to all the girders. Live load deflections due to the user-defined vehicle
and fatigue live load are also provided for information. Live load deflections are checked
against the span length divided by the user-input live load deflection factor input on the Loads
Form (Article 3.5.3). A warning message is printed at the beginning of the span output if the
computed live load deflection in the span exceeds the span length divided by the user-input live
load deflection factor, and the design process continues. LRFD Simon will not attempt to
reduce excessive live load deflection; that is the user’s responsibility.
Total non-composite dead-load deflections are output along with the deflections due to the
girder weight plus any partial dead loads that are specified. Deflections due to the composite
dead load (without the future wearing surface) are also provided. These deflections can be
used for camber calculations.
For the live-load moments, the maximum moment is never negative and the minimum moment
is never positive.
If the structure is symmetrical, detailed information is required only for the spans on the left
side of the bridge centerline, and the analysis output is similarly reduced.
The Load and Resistance Factor Design Method in the AASHTO Specifications is based on the
strength of individual member cross sections and presumes an elastic analysis to determine
moments and forces; thus, an elastic analysis is performed in LRFD Simon. The additional
strength from redistribution of internal forces in continuous spans to accommodate complete
collapse mechanisms is not considered in the analysis.

For a box girder, a conventional elastic analysis is performed in which the bottom-flange
longitudinal stiffeners and the sloping web are not considered in the computation of the girder
stiffness. This omission simplifies the program and should not significantly alter the moment
envelopes. Lastly, the weight of the bottom-flange tee stiffeners is not internally included by
LRFD Simon in the non-composite dead load. The user can compensate for this by including the
weight of the tees in the non-composite dead load (the non-composite partial dead loads may
be useful for this purpose – Article 3.10.5).
All analysis results that are output are unfactored and are so labeled.
5.3 Design
5.3.1 General
In LRFD Simon, the current design and analysis results (i.e., the results of the last computed
analysis-design cycle) are compared with a set of permissible criteria based on the provisions of
the AASHTO LRFD Bridge Design Specifications, and on criteria that the user has entered.
Deviations from the AASHTO criteria, specifically items that are currently not covered or
considered in LRFD Simon, are summarized in Article 6.
This section describes the calculation of the factored loads and stresses that are used in the
design checks at each limit state, the concept of a performance ratio and the procedures used
to determine the locations of the sections are checked, the redesign process that is used by
LRFD Simon whenever the LRFD Design run option is chosen (Article 5.1.2), the optional web
depth optimization process, and the bill of materials and optional shear-connector design
reports that are produced whenever a successful design has been achieved.
5.3.2 Calculation of Factored Loads/Stresses
5.3.2.1 Strength Limit State
To determine the critical factored load combination at the strength limit state, LRFD Simon first
multiplies the DC and DW loads by the following four sets of load factors for the Strength I load
combination taken from AASHTO LRFD Table 3.4.1-2:
 Maximum DC and DW load factors (1.25 and 1.50)

 Minimum DC load factor (0.90) and Maximum DW load factor (1.50)
 Maximum DC load factor (1.25) and Minimum DW load factor (0.65)
 Minimum DC and DW load factors (0.90 and 0.65)
Each of the above factored dead load combinations is then combined with the factored
maximum live load moment (load factor = 1.75), and the total critical factored load
combination is saved for the stress calculations. A similar process is followed with the minimum
factored live load (load factor = 1.75). Note that the load modifier, η (AASHTO LRFD Article
1.3.2.1), is always taken equal to 1.0 in LRFD Simon and cannot be modified by the user.
The total unfactored stress at the top of the deck slab is then calculated using n-composite
section properties (using DC2, DW and live load moments only). The resulting stress on the
transformed section is then divided by the modular ratio, n, to give the stress in the concrete
slab. If the resultant stress in the slab is compressive, then the positive bending composite
section properties are used for the calculation of the factored Strength I stresses in the steel
section acting on the composite section. If the slab stress is tensile, then negative bending
section properties are used.
For positive bending, the long-term (3n) composite section is used for composite dead loads,
and short-term (n) composite section is used for live loads. If the neutral axis is in the slab or
concrete haunch, the tension concrete is not considered in the computation of the section
properties. For negative bending, only the steel section and the longitudinal reinforcement are
used for both the short-term and long-term moments applied to the composite section. Non-
composite dead load stresses for both positive and negative bending are computed using the
properties of the steel section only.
The elastic depths of the web in compression, Dc, that are output in the Detailed Information
table for strength are computed as specified for positive and negative flexure in AASHTO LRFD
Article D6.3.1. (Note that the value of Dc that is output for construction and the deck pours is
computed for the steel section only).
The computed individual factored stresses are algebraically summed. Maximum and minimum
stresses are computed at several vertical locations on each cross-section checked, including at
the rebars and at the top of the slab.
Only the Strength I load combination is considered by LRFD Simon; the user is responsible for
checking other applicable strength load combinations. For strength limit state design checks for
constructibility and the deck pours, LRFD Simon does consider the special load combination
specified in AASHTO LRFD Article 3.4.1.2 for loads applied to the fully erected steelwork (load
factor = 1.40 applied to the DC loads only).
5.3.2.2 Service Limit State
At the service limit state, the Service II load combination is considered by LRFD Simon (DC and
DW load factors = 1.0; live load factor = 1.30).
If the user indicates that the deck slab meets the AASHTO LRFD Article 6.10.1.7 criteria on the
Material Properties Form (Article 3.4), and LRFD Simon determines internally that the Service II
tensile stress in the slab at the section under consideration is less than 2fr, where fr is the
modulus of rupture of the concrete specified in AASHTO LRFD Article 6.10.1.7, the slab is then
considered effective for both positive and negative flexure for the calculation of the Service II
flexural stresses in the steel girder at the section under consideration due to loads applied to
the composite section (see AASHTO LRFD Article 6.10.4.2.1). The long-term (3n) composite
section is used for composite dead loads, and short-term (n) composite section is used for live
loads. Non-composite dead load stresses are computing using the properties of the steel
section only. The elastic depths of the web in compression, Dc, that are output in the Detailed
Information table for service in this case are computed as specified for positive and negative
flexure in AASHTO LRFD Article D6.3.1 using AASHTO LRFD Eq. D6.3.1-1.
If the Service II tensile stress in the slab at the section under consideration is greater than 2fr,
the slab will not be considered effective for negative flexure for the calculation of the Service II
flexural stresses in the steel girder at the section under consideration due to loads applied to
the composite section. Stresses due to negative flexure and Dc in this case are computed using
the section consisting of the steel section plus the longitudinal reinforcement, or the steel
If the user indicates that the slab does not meet the AASHTO LRFD Article 6.10.1.7 criteria on
the Material Properties Form, the slab will not be considered effective for negative flexure for
the calculation of Service II flexural stresses in the steel girder at all sections in the member,
due to loads applied to the composite section. Stresses due to negative flexure and Dc in this
case will be computed using the section consisting of the steel section plus the longitudinal
reinforcement, or the steel section alone, as applicable.
Live load deflections are computed by LRFD Simon using a live load factor of 1.0.
5.3.2.3 Fatigue Limit State
At the fatigue limit state, if the user indicates that the slab meets the AASHTO LRFD Article
6.10.1.7 criteria on the Material Properties Form (Article 3.4), LRFD Simon will consider the slab
effective for both positive and negative flexure for the calculation of dead load and live load
stresses and live load stress ranges for fatigue design at all sections in the member due to loads
applied to the composite section (see AASHTO LRFD Article 6.6.1.2.1). The long-term (3n)
composite section is used for dead loads, and short-term (n) composite section is used for live
loads.
If the user indicates that the slab does not meet the AASHTO LRFD Article 6.10.1.7 criteria on
the Material Properties Form, the slab will not be considered effective for negative flexure by
LRFD Simon for the calculation of dead load and live load stresses and live load stress ranges for
fatigue design due to loads applied to the composite section. Stresses due to negative flexure
in this case will be computed using the section consisting of the steel section plus the
longitudinal reinforcement, or the steel section alone, as applicable.

Live load stress ranges are computed by LRFD Simon for both the Fatigue I (load factor = 1.75)
and Fatigue II (load factor = 0.80) load combinations, as applicable. The unfactored dead load
stress is also computed and is used by LRFD Simon to determine whether or not the detail
under consideration is subject to a net tensile stress under the sum of the stresses due to the
unfactored dead load and the Fatigue I load combination indicating that fatigue must be
checked (see AASHTO LRFD Article 6.6.1.2.1). In such cases, the detail is checked for either the
Fatigue I or Fatigue II load combination depending on the fatigue detail category (see AASHTO
LRFD Table 6.6.1.2.3-1) and the single lane average-daily truck traffic, (ADTT)SL (see AASHTO
LRFD Table 6.6.1.2.3-2). Further information on fatigue design in LRFD Simon is provided in
Article 5.3.9.
5.3.3 Performance Ratio & Location of Section Checks
In LRFD Simon, a parameter termed the performance ratio is computed for each of the design
criteria and is defined as:
Calculated value
Performanc e Ratio 
Permissibl e value
A ratio greater than the user-input maximum performance ratio (Section 3.2.2; default = 1.0)
indicates that the current design is invalid (such a ratio is flagged in red in the output), whereas
a ratio less than the user-input maximum performance ratio indicates that a parameter is below
the permissible value.
In LRFD Simon, the investigation proceeds one span at a time, starting at the left end of the left
span and moving to the right. A performance ratio is computed for each design criterion at the
following cross-sections:
 Left end of the span;

 Splice (bolted or welded) in either the top or bottom flange;
 Splice (bolted or welded) in the web;
 Point of total maximum moment (located by parabolic interpolation);
 Locations where studs are interrupted near an interior support;
 Right end of the span.
The factored stresses in the bottom flange of the steel section at the strength limit state (Article
5.3.2.1) are used to determine if the section is in positive or negative bending. If the factored
stress in the bottom flange using the critical factored load combination for the minimum live
load moment is compressive, then the section is considered to experience negative bending. If
the factored stress in the bottom flange using the critical factored load combination for the
maximum live load moment is tensile, then the section is considered to experience positive

bending. If both situations are true, the section is checked for both positive and negative
bending.
At a section where a splice (bolted or welded) exists, only one side of the section is checked;
the weaker section at the splice as determined by (in order) the side with the:
1. Smaller bottom flange thickness

2. Smaller bottom flange width
3. Smaller bottom flange yield strength
4. If a box girder, the smaller number of bottom-flange longitudinal stiffeners
5. If a box girder, the smaller area of individual bottom-flange longitudinal stiffeners
6. Smaller top flange thickness
7. Smaller top flange width
8. Smaller top flange yield strength
9. Smaller web thickness
10. Smaller web yield strength
11. If a bottom web longitudinal stiffener is present, the smaller stiffener thickness
12. If a top web longitudinal stiffener is present, the smaller stiffener thickness
13. If a bottom web longitudinal stiffener is present, the smaller stiffener area
14. If a top web longitudinal stiffener is present, the smaller stiffener area
15. Transverse stiffener spacing (for this check only, the weaker side is the side with the
larger value)
As soon as one of these criteria is met, the weaker section is chosen. It is not a cumulative
check. For example, if the bottom flange on the left side of the splice is thinner than the
bottom flange on the right side, but the top flange on the left side is thicker than the top flange
on the right side, the left side will be chosen as the weaker side because the bottom flange
thickness check is done before the top flange thickness check. At each section checked, the
side checked is indicated in the output if a splice is sensed.
If a web splice occurs at a flange splice location, the web considered is that on the weaker side
of the cross-section. In certain cases, it may be possible that the section checked based on the
rules used to determine the weaker section may not check the weaker web at a web splice.
The user can ensure that the weaker web is checked by appropriately offsetting a web splice
from a flange splice in LRFD Simon by a small amount.
LRFD Simon will check a section at any defined web range (even if an actual web splice is not
present). This permits a user the freedom to add checks at selected locations. For example, in
the case of a box girder with a longitudinally stiffened bottom flange, the user should check a
bottom-flange splice where the tees terminate, since a thicker unstiffened flange may be on the
weaker side and will not be the side checked by LRFD Simon. At such a section, it may be
prudent to include an additional web range on the Web Cross-Section Information Form (Article

3.11.2) offset slightly into the thicker-flange section. In this way, LRFD Simon will then
effectively check both sides of the splice. Additional web ranges can also be used to ensure
that fatigue of connection-plate welds will be checked at each cross-frame location.
For each design check that is made at a section, in addition to the performance ratio and a
description of the specific design check that is made, the specific AASHTO LRFD specification
article and year are also output.
5.3.4 Redesign
5.3.4.1 General
When the LRFD Design run option is selected (Section 5.1.2), and a performance ratio is above
the user-input maximum performance ratio, redesign is mandatory; that is, the flanges must be
made larger and/or the web must be made thicker. If the performance ratio is below the user-
input maximum performance ratio (Article 3.2.2; default = 0.90), redesign is made only if a
performance ratio is below this ratio; that is, flange thicknesses will be made smaller and/or the
web thickness may be reduced if permitted by the user. The program will continue to
automatically cycle the design until all ratios fall in-between these two user-input values.
During the design process, LRFD Simon compares the girder weight (total weight of the web,
flanges and any longitudinal stiffeners) and the maximum performance ratio with those found
in each previous design cycle. The girder weight is the objective, or merit, function used to
compare different feasible designs. A design is feasible if the maximum performance ratio is
not above the user-input maximum performance ratio. LRFD Simon attempts to find a
minimum-weight design within the applicable constraints.
Based on these checks, the decision is made to perform another analysis-design cycle (using the
new trial design), to stop the program (if a significant error is encountered), or to prepare a bill
of materials (Article 5.3.6). LRFD Simon assumes that if both the weights and corresponding
maximum performance ratios of any two cycles are equal, the same design has been
formulated twice and another analysis-design cycle is not attempted (unless a previous cycle
found an acceptable design).
The initial selection of the flange splice locations (bolted and welded), girder depths, and flange
widths must be made by the user. This was done because it is assumed that the user is familiar
with bridge design and can select suitable values of these dimensions. Experience with LRFD
Simon indicates that a more efficient final design may result if the input design is slightly on the
unconservative side. Also, if a welded flange splice is specified, the relative plate thicknesses
should agree with those intuitively expected.
Should a redesign be required, the following variables may be changed by LRFD Simon: flange
width, flange thickness, and/or web thickness.
In the design routines, as in manual design procedures, the thickness of a flange is usually
controlled by the major-axis bending moment, and the thickness of a web by the shear force.
The flange thickness is automatically varied until the maximum-axis bending stress (in
combination with any lateral bending stress) is less than or equal to the permissible value. The
resulting thickness will not fall outside the minimum and maximum flange thicknesses input by
the user on the General Properties Form (Article 3.2).
The web thickness is automatically selected to satisfy the shear stress and depth/thickness
requirements for girder webs with or without stiffeners as specified in the input data (Article
3.11.2). If transverse stiffeners are specified, LRFD Simon will select the thinnest permissible
stiffened web, and later in the bill-of-materials routines, will calculate the required stiffener
spacing for this thickness (once a successful design has been obtained). LRFD Simon does not
automatically consider other possible combinations of web thickness and stiffener spacing, and
does not compare the economy of girders with and without transverse and longitudinal web
stiffeners. However, the user can ensure that the input web thickness is not reduced (Article
3.11.2); thus, a partially stiffened web can be designed, which will not result in the thinnest
permissible stiffened web.
The flange width is only increased in two situations: 1) if the flange width is less than the D/6
requirement given by AASHTO LRFD Equation 6.10.2.2-2, or 2) if the flange thickness exceeds
either the user-input maximum plate thickness (Article 3.2.2) or 4", whichever is smaller. If the
flange width fails the D/6 check, the flange width is increased to satisfy the check and the
flange thickness is maintained. If the flange width is increased to satisfy the flange thickness
requirement, the flange thickness is set to the user-input maximum plate thickness and the
flange width is set such that the total area of the flange is not less than the total area of the
original flange. The flange widths are never decreased from their initial user-input values, or
their increased values.
After the flanges have been resized according to the specification check ratios, the flange
proportions are checked against AASHTO LRFD Specification Equations 6.10.2.2-1 and 6.10.2.2-
3. If these checks fail, the flange thicknesses are increased to satisfy the equations, then
rounded up to the next highest acceptable flange thickness.
The web depth is never changed during the design. It is possible that a different web depth
could result in a girder of greater economy. If the user desires to check this, the user must
either: 1) enter a new web depth and re-run the program, or 2) perform a web-depth
optimization as described in Article 5.3.5.
The procedure of changing only certain dimensions permits the program to usually find an
acceptable design and simplifies the program, but puts a larger share of the design

responsibility on the user. LRFD Simon does not attempt to bring the performance ratio to the
user-input maximum performance ratio on the subsequent design cycle; rather, it attempts to
move about half the distance between the actual performance ratio and the user-input
maximum performance ratio. This reduces the chance of overcorrecting and fluctuating the
ratio during the design cycles. This procedure is not adversely affected by ratios close to the
user-input maximum performance ratio because thicknesses and widths are restricted to
discrete values; thicknesses are incremented to the nearest 1/16 in. up to and including 2
inches, and to the nearest 1/8 in. above 2 inches. Widths are incremented to the nearest 1/8
in.
A list is given in the table below that summarizes the specification checks that can result in a
change of a plate size and which plate will be changed.
Specification
Article Specification Description Dimension Changed
6.6.1.2 Fatigue: Bottom Flange Base Metal Bottom Flange Thickness
6.6.1.2 Fatigue Top Flange Base Metal Top flange thickness
6.6.1.2 Fatigue: Bottom Flange Splice Bottom flange thickness
6.6.1.2 Fatigue: Top Flange Splice Top flange thickness
6.6.1.2 Fatigue: Bottom flange / web fillet weld Bottom flange thickness
6.6.1.2 Fatigue: Top flange / web fillet weld Top flange thickness
6.6.1.2 Fatigue: Bearing stiffener at bottom flange Bottom flange thickness
6.6.1.2 Fatigue: bearing stiffener at top flange Top flange thickness
6.6.1.2 Fatigue: transverse stiffener at bottom flange Bottom flange thickness
6.6.1.2 Fatigue: transverse stiffener at top flange Top flange thickness
Fatigue: connection plate at bottom flange

6.6.1.2 (bolted) Bottom flange thickness
6.6.1.2 Fatigue: connection plate at top flange (bolted) Top flange thickness
Fatigue: connection plate at bottom flange

6.6.1.2 (welded) Bottom flange thickness

Specification
Fatigue: connection plate at top flange

6.6.1.2 (welded) Top flange thickness
6.6.1.2 Fatigue: top flange adjacent to stud Top flange thickness
6.10.3.2.1 Web bend-buckling (Constructibility) Web thickness
Top or bottom flange thickness

Compression flange nominal yielding (depending on stress at the top of
6.10.3.2.1 (constructibility) web)

(depending on state of flexure of
6.10.3.2.1 Compression flange buckling (constructibility) the section)

Tension flange nominal yielding (depending on state of flexure of
6.10.3.2.2 (constructibility) the section)

Compression flange nominal yielding (depending on state of flexure of
6.10.3.2.3 (constructibility) the section)
Top flange service limit state permanent

6.10.4.2.2 deflections Top flange thickness
Bottom flange service limit state permanent

6.10.4.2.2 deflections Bottom flange thickness
Compression flange service limit state bend-

6.10.4.2.2 buckling Web thickness

(depending on which flange has the
6.10.7.1.2 Flexure - compact, composite, positive flexure greater stress)
Flexure - noncompact, composite, positive

6.10.7.2.2 flexure, top flange Top flange thickness

Specification
Flexure - noncompact, composite, positive

6.10.7.2.2 flexure, bottom flange Bottom flange thickness
6.10.7.3 Flexure - composite, positive flexure, ductility Compression flange thickness

Flexural resistance: discretely braced flange in (depending on state of flexure of
6.10.8.2.2 compression the section)

6.10.8.2.3 compression the section)

6.10.8.1.2 tension the section)
Flexural resistance: continuously braced flange

6.10.8.1.3 in compression Top flange thickness
Web D/tw <= 150 and no longitudinal web

6.10.2.1.1-1 stiffener (web proportion limit) Web thickness
Web D/tw <=300 and longitudinal web stiffener

6.10.2.1.2-1 (web proportion limit) Web thickness
6.10.2.2-1 Top flange b/(2*t) <= 12 Top flange thickness
6.10.2.2-2 Top flange b >= D/6 Top flange width
6.10.2.2-3 Top flange t >= 1.1 * tw Top flange thickness
6.10.2.2-1 Bottom flange b/(2*t) <= 12 Bottom flange thickness
6.10.2.2-2 Bottom flange b >= D/6 Bottom flange width
6.10.2.2-3 Bottom flange t >= 1.1 * tw Bottom flange thickness
5.5.3.2 Fatigue: reinforcing bars Top flange thickness

Specification
Web D/tw <= 150 and no longitudinal web

6.11.2.1.2-1 stiffener (web proportion limit) Web thickness
Web D/tw <= 300 and longitudinal web stiffener

6.11.2.1.3-1 (web proportion limit) Web thickness
6.11.2.2-1 Top flange b/(2*t) <=12 (box girder) Top flange thickness
6.11.2.2-2 Top flange b >= D/6 (box girder) Top flange width
6.11.2.2-3 Top flange t >= 1.1 * tw (box girder) Top flange thickness
Web bend-buckling (constructibility) (box

6.11.3.2-2 girder) Web thickness
Top flange service limit state permanent

6.11.4 deflection Top flange thickness

Flexure - compact, composite, positive flexure (depending on which flange has the
6.11.7.1.2 (box girder) larger stress)
Flexural resistance: continuously braced flange

6.11.8.1.2 in tension, negative flexure (box girder) Top flange thickness
Tension flange nominal yielding

6.11.3.2 (constructibility) (box girder) Bottom flange thickness
Bottom flange service limit state permanent

6.11.4 deflection (box girder) Bottom flange thickness
Bottom flange thickness and

Compression flange nominal resistance stiffness (box girder flange
6.11.3.2-1 (constructibility) (box girder) longitudinal stiffeners)
Bottom flange thickness and

Flexural resistance: box flange in compression, stiffness (box girder flange
6.11.8.1.1 negative flexure longitudinal stiffeners)
6.10.9.2 Nominal shear resistance of unstiffened web Web thickness

Specification
Nominal shear resistance of stiffened web

6.10.9.3.2 interior panel Web thickness
Nominal shear resistance of stiffened web end

6.10.9.3.3 panel Web thickness
6.10.3.3 Shear (constructibility) Web thickness
6.10.5.3 Special fatigue requirements for webs Web thickness
If the user-input redesign performance ratio, corresponding to the performance level above
which redesign of a variable is not attempted, is set too high, it can disturb the convergence
process. For example, if this ratio is 0.90 (the default value) and the following web thickness
and performance ratio occur on successive cycles, convergence may be erratic:
Cycle Web Thickness, in. Web Performance Ratio

n 0.5625 0.88
n+1 0.500 1.05
This behavior occurs in this case because there is no discrete web thickness that will result in a
performance ratio between 0.9 and 1.0. For this example, a user-input redesign performance
ratio of 0.87 would help the convergence; however, this reduced value may cause the flanges
to be overdesigned. Alternatively, on an additional run, the user could fix the minimum web
thickness in this example at 0.5625 inches.
5.3.4.2 Box Girders
The design of the bottom flange of box girders requires special considerations. When the
bottom flange is always in tension, such as in a simple span, the design is similar to that of an I-
girder. Note that because the box section is assumed to satisfy the cross-section restrictions
specified in AASHTO LRFD Article 6.11.2.3 (Article 3.3.1), shear due to St. Venant torsion is not
considered by LRFD Simon in the design of the bottom flange. However, when the bottom
flange is in compression, such as in certain sections of a continuous span, the nominal flexural
resistance of the flange is related to the flange buckling strength, and may be considerably
below the yield strength of the flange material. AASHTO LRFD Article 6.11.8.2 provides
equations to determine the buckling strength of a box-girder bottom flange, and this strength is
a function of the flange width, thickness, and the number and size of flange longitudinal
stiffeners.

LRFD Simon uses a procedure for redesigning a box-girder bottom flange for a new iterative
cycle that is different from the procedure for checking the acceptability of the bottom flange on
the current cycle. The redesign procedure is approximate, whereas the checking procedure
follows the AASHTO specifications. In the redesign, LRFD Simon selects the most economical
combinations of plate thickness and stiffener number and size by the following procedure.
The plate thickness and bottom-flange stiffener size are selected from tables of acceptable
plate thicknesses and stiffener sizes that are stored in LRFD Simon. The user may input a
minimum bottom-flange thickness on the Box Girder Properties Form (Article 3.9) that will
override the value of minimum flange thickness entered on the General Properties Form
(Article 3.2); the default value is 0.3125 in. The table of plate thicknesses is used for I-girders as
well as for box girders. The table of acceptable stiffener sizes includes 10 WT (tee) sections. A
WT section is cut from a W (wide-flange) section. Each tee has a different depth and the depths
range from 4 to 18 inches, as shown in the following table:
WT 4 X 9 (A = 2.63 in2) WT 12 X 34 (A= 10.0 in2)

WT 7 X 11 (A= 3.25 in2) WT 13.5 X 42 (A= 12.4 in2)
WT 8 X 15.5 (A= 4.56 in2) WT 15 X 49.5 (A= 14.5 in2)
WT 9 X 23 (A= 6.77 in2) WT16.5 X 59 (A= 17.3 in2)
WT 10.5 X 28.5 (A = 8.37 in2) WT 18 X 67.5 (A= 19.9 in2)
WT 18 X 150 (A = 44.1 in2)
Each tee was selected to be at or near the most efficient available tee of that depth; that is,
with the highest ratio of moment of inertia about the stem to cross-sectional area. All tees
meet the AASHTO width-to-thickness ratios for outstanding elements (AASHTO LRFD Article
6.11.11.2) for Grade 36 and Grade 50 steels. LRFD Simon assumes that the tees have the same
yield strength and range as those of the bottom flange (note that tees may not be available in
higher grades of steel). The flange tees are excluded from the moment of inertia used in
calculating the distribution of moments and deflections, but are included in calculating the
sectional properties for stress calculations. The flange tees are also included in the area of the
bottom flange in hybrid-girder computations because the tee and the bottom-flange plate are
assumed to have the same yield strength and behave as an effective flange. In specifying a
minimum or maximum tee area, the area does not have to correspond to a tee area as listed
above; however, the user should ensure that at least one tee exists between the input limits.
According to AASHTO, the required moment of inertia of a longitudinal flange stiffener, Iℓ, must
satisfy the following:
I  wt3fc

in which tfc is the bottom-flange thickness, w is the lateral spacing of the stiffeners (which must
be uniform as required by AASHTO), and ψ is a parameter that depends on the number of
stiffeners, n, and the desired buckling coefficient, k, for the flange. Note that k cannot exceed
4.0. Thus, the required stiffener size can be calculated from the preceding equation for any
combination of flange thickness, number of stiffeners, and desired buckling coefficient.
LRFD Simon initially computes an approximate required flange force that is equal to the product
of the calculated bottom-flange maximum stress times the sum of the areas of the bottom
flange and tees. The first cycle always assumes that the user-input design is for an unstiffened
bottom flange so that the corresponding performance ratios are usually high in regions of
compression. LRFD Simon then computes a flange force for all combinations of n and k in
conjunction with the lightest trial flange thickness. Values of k ranging from 0.5 to 4.0 in
increments of 0.5 are tried. If none of the combinations provides a flange force equal to or
greater than the required flange force, the process is repeated with a thicker flange plate until
one or more combinations of n and k with this thickness provide the required force. If a
bottom-flange section is always in tension, no tees are specified by the program for that
section. The cost indexes of each satisfactory combination are calculated from the fabrication
cost factors input by the user (Article 3.12.3). The process is then repeated for the next thicker
flange plate. If all satisfactory combinations with this thickness are more expensive than one of
the satisfactory combinations with the next thinner flange plate, the program does not check
any more combinations.
After all design checks have been made for the original design resulting from the above process,
a new design cycle is started. In this cycle, the bottom-flange compression stress is checked
against the appropriate AASHTO formulas for the stiffener-flange configuration developed on
the previous cycle. This check is made by calculating the exact stress from the selected
dimensions rather than working with an approximate required flange force. The design cycles
continue until a satisfactory overall design is achieved in the same way as is done for I-girders.
For all design cycles but the first cycle, LRFD Simon indicates the number and size of tees for
each bottom-flange section in the input echo for that cycle. This method of designing a box-
girder bottom flange may result in a different size and/or number of tees for each bottom-
flange section and consequently may result in stiffeners that are not continuous from one
section to the next. This may be undesirable, and therefore, LRFD Simon provides the user with
two options to control the many possible combinations. First, on the Box Girder Properties
Form (Article 3.9), the user can specify either or both the maximum and minimum tee areas to
be considered; if both are selected as the same, only that tee size is considered. Second, the
user can specify the maximum number of tees per box to be considered (0, 1 or 2). AASHTO
LRFD Article C6.11.11.2 suggests using flange transverse stiffeners if 2 or more flange
longitudinal stiffeners are used. Flange transverse stiffeners are not considered in LRFD Simon.
The user also exerts an indirect control over the bottom-flange design by the ratio of the
fabricating costs for the tee and flange; a high ratio would tend to result in smaller and fewer
tees than a low ratio.

The design of the bottom compression flange against buckling is more sensitive to changes
between design cycles than the bottom flange of an I-girder. One type of sensitivity can be
illustrated by the following example. Assume that an AASHTO M270 Grade 36 (ASTM A709
Grade 36) steel bottom flange is located in a region subjected to high positive moment and low
negative moment. For design cycle N, assume that this flange is unstiffened and experiences
factored stresses of +34.0 ksi and -2.0 ksi, with corresponding performance ratios of 0.94
(yielding) and 0.90 (buckling). The new design of this flange for the next cycle is unchanged,
although other parts of the structure are changed. For cycle N+1, because of changes in
stiffness and dead load, the stresses are now +33.5 ksi and -2.5 ksi, with corresponding
performance ratios of 0.93 (yielding) and 1.125 (buckling). Thus, the relatively small stress
change of 0.5 ksi causes a 22.5 percent change in the performance ratio for buckling, even
though the bottom-flange geometry was not changed. Also, this bottom flange has high
performance ratios for both tension and compression; a condition not typically encountered in
an I-girder.
The sensitivity of the bottom compression flange can create a convergence problem in LRFD
Simon, since it is possible that no bottom-flange geometry exists that will yield a performance
ratio between the minimum specified by the user and 1.0. Therefore, the user can optionally
input a minimum performance ratio for redesign that will be applicable only to the bottom
flange in compression on the Box Girder Properties Form (Article 3.9). This value will normally
be lower than the value used for the other components and thus will not penalize the entire
girder.
Approximate moments of inertia based on a vertical web of the user-specified thickness and no
longitudinal bottom-flange stiffeners are used for determining the moment distribution and
deflections in continuous box girders. However, the correct sloping-web dimensions and flange
stiffeners are used to determine the section properties for stress calculations. As specified in
AASHTO LRFD Article 6.11.9, the web shear is computed by dividing the vertical shear by cos θ,
where θ is the angle of inclination off the vertical of the web. The web is designed as if it were a
web equal in depth to the inclined depth of the web. The correct sloping web is also used in the
weight computations.
LRFD Simon allows the user to enter a variable depth box girder with sloping webs. The
program does not maintain a constant distance between the top flanges for this case. If it is
desired to maintain a constant distance between the top flanges, the user must enter the
appropriate varying bottom flange widths in the regions where the web depth varies.
5.3.5 Web Depth Optimization
The optional web depth optimization function assists the user with optimization of the vertical
web depth of an I- or Box Girder. When the web depth optimization function is turned on,

LRFD Simon generates a series of trial-design input files for the LRFD Simon engine from a
starting design input file. The generated input files differ from the starting input only in the
vertical web depth. Each of these input files is processed automatically by the analysis engine,
and a table is prepared listing the depth, weight, and cost (based on user-input cost factors) for
the depths that have acceptable designs. The user may specify a web depth optimization for
either the LRFD Design or LRFD Analysis run options. However, if specified for the LRFD
Analysis run option, the same flanges will be used for all runs, which will probably not result in
the most efficient designs.
The starting design selected by the user should be a valid design so that at the other depths,
the number of design cycles is minimized and the chances of finding an acceptable design are
increased. However, the program will continue to run even if the starting design is not a valid
design. Other depths may result in a valid design.
There are five required input items for web depth optimization, which are entered on the Web
Depth Optimization Form (Article 3.13). ′Web Optimization′ on this form must be set to ′Yes′ in
order to turn on the web depth optimization function. The other input values on this form are
used to modify the starting web depth during the process. A fixed depth variation will represent
a vertical relocation of the top flange. A percentage depth variation could be used in a
haunched design where it is desired to keep the ratio of prismatic-to-haunched depth the same
for all the generated designs. The user should ensure that all the parameters specified for the
starting design, such as flange width, are appropriate over the entire specified range of depths.
It is helpful to position the starting design near the center of the depth range that will be used
for the web depth optimization.
For a box girder with sloping webs (see Section 5.3.4.2), the vertical web depth is varied. The
user may initially investigate a large depth range using a large depth increment and then, based
on the results, select an appropriate smaller depth range to investigate with a smaller depth
increment.
Before the LRFD Simon analysis engine is run, the web depth optimization interface program
creates a number of input files with the names ′<original file>_below#.dat′ and ′<original
file>_above#.dat′, where ′<original file>′ is the name of the original input file (without the file
extension), and ′#′ refers to the number of increments below or above the original web depth.
For example ′EX1_ABOVE5.DAT′ is created from the input file ′EX1.DAT′, and the web depth is
five increments deeper than the original web depth.
These files are created each time the original input file is run with the web depth optimization
function turned on, and will be overwritten on subsequent runs of the original input file. If
input or output from a particular web optimization run should be saved, it is up to the user to
copy or rename the files before running the program with optimization again. Note that the
Command Prompt window will appear and disappear several times throughout the

optimization runs. The window will appear once for each increment above and below the
original depth, and once for the original input file. The Command Prompt windows must be
allowed to open and close with no interference from the user.
A sample tabular output of web depth, tonnage, and cost from the web depth optimization
function is shown for the acceptable designs, as well as the filenames of any runs that did not
complete successfully. The tabular output also lists the title of the LRFD Simon job. This
information is provided in a text output file named <original file>.DPV. A sample .DPV file for
the LRFD Simon Tutorial input file generated within the Exhibits of this User’s Guide is given
below. The web depth for the starting design in the original input file in this case was 67
inches:

LRFD Simon Version 10.1.1.12 2015-FEB-11 13:32:32
Vehicle library: NSBA_Vehicle_Data.txt

Program library: NSBA_simon_library_data.txt
Agency library: NSBA_library_data.txt
Job Name: NSBA Example

Project Name: Three-Span Continuous Straight Composite I-Girder Bridge
Description: 140'-175'-140'
LRFD SIMON Tutorial

Three-Span Continuous I-Girder (140'-175'-140')
WEB DEPTH VARIATION ANALYSIS OUTPUT
More information about the web optimization algorithm can be found in the
program User's Guide in the Program Methodologies / Web Depth Optimization
section.
In the filenames given on the following table, BELOW designates design runs
with web depths LESS than the original web depth, while ABOVE designates runs
with web depths greater than the original. The numbers at the end of each of
the filenames refer to the number of increments above or below the original
web depth considered in the file. For example, a file ending in "BELOW2"
considers a web depth two increments (either fixed or percentage) below the
original input web depth.
The filename without ABOVE or BELOW at the end of the filename is the original
run with web depths designated by the user.
If any expected output files are not shown here, it is likely that the run for
that increment ended abnormally (usually, the program stopped due to an error)
All of files listed below (as well as any expected files that have crashed are
are available in the same folder as the original input file. Please open the
desired input file to view the available program input and output. Please
remember to change the WEB DEPTH OPTIMIZATION option to NO so that another web
optimization is not attempted.
DEPTH VARIATION ANALYSIS

========================
Depth Weight Cost

Filename Inch Tons $
------------------------- ---------- ---------- ----------
SIMONTUTORIAL_BELOW3 61.00 245.67 513546
SIMONTUTORIAL 67.00 239.88 502815
SIMONTUTORIAL_ABOVE1 69.00 240.66 504648
The .DPV file will be created or overwritten upon each execution of LRFD Simon for input files
with web depth optimization turned on. Thus, if it is desired to save this .DPV output file, it
should be copied to another file, renamed, or else printed before re-execution of LRFD Simon.
Each of the input files created by the web depth optimization function can be separately
opened and independently run in order to examine the output. However, if the user desires to
run LRFD Simon for a particular input file again, be sure to change ′Web Optimization′ to ′No′ on
the Web Depth Optimization Form (Article 3.13), or another web depth optimization will be
performed that is centered on the web depth given in that particular file.
5.3.6 Bill of Materials
5.3.6.1 General
When an acceptable design has been detected by LRFD Simon, other details of the design are
computed in the bill of materials.
For the regions of the girder web specified by the user, the size and location of transverse
stiffeners are calculated. Transverse stiffeners are placed at the maximum permitted distance,
thus giving the minimum number of stiffeners and, generally, a non-uniform spacing. Also, a
transverse stiffener may be placed at the limits of each web section. The user may later
manually adjust this spacing. In a region specified by the user as transversely stiffened, if a
location is encountered where a stiffener is not required by AASHTO, none is added. Further
information on the transverse-stiffener design is given below in Article 5.3.6.2.
The webs, flanges, and web and bottom-flange longitudinal stiffeners are tabulated along with
their location, yield strength, weight, length, thickness, and width. Using a unit weight of
0.2833 lbs/in3, the total weights of all the steel-plate components in the bridge (for one girder)
are then listed. For a parabolic haunch, the web and bottom flange are divided into five linear
sections to compute the steel volume. For this computation, the top longitudinal stiffener is
assumed parallel to the top flange, and the bottom longitudinal stiffener is assumed parallel to
the bottom flange. The indicated width of the web plate is the inclined web depth for box
girders with sloping webs. The area and size of any bottom-flange tee stiffeners are listed
within the thickness and width columns of the table.
Estimated costs are computed for the girder, and are listed both by span and by component.
The estimated costs are based on the user-input cost factors (Article 3.12). The user may enter
material unit costs per ton for each yield strength (total costs for each yield strength are
tabulated), and relative assumed fabrication cost factors for each component. Separate
fabrication cost factors may be entered for the web, flange, web and bottom-flange
longitudinal stiffeners, and web transverse (including bearing) stiffeners.
Because a user may wish to compare designs for I- and box girders for the same bridge, and
because the two types of designs may use a different number of girders, the total cost and
weight for the bridge are also given as the cost (or weight) per girder times the number of
girders. The total weight and cost include (separately) the weight/cost of the transverse and

bearing stiffeners. Shear-connector costs are not included in the computation of the estimated
costs.
5.3.6.2 Transverse Stiffener Design
The spacing of the transverse stiffeners and the design of the transverse-stiffener plates is done
in the bill-of-materials routines at the completion of the design routines. The results are output
in the bill of materials. The same routines are used for I- and box girders. For box girders with
sloping webs, the inclined web depth is used in the transverse-stiffener design.
5.3.6.2.1 Transverse Stiffener Spacing
Transverse stiffeners may be designed for any specified web section - either part or all of a
span. The envelope of the absolute value of the factored sum of the non-composite and
composite dead-load shears plus the absolute value of the factored live-load shear is
constructed.
After finding the point of minimum shear, stiffeners are designed starting at the left end of the
web section and proceeding toward the right end of the web section (left pass). If a point is
reached where transverse stiffeners are not required by AASHTO, the left pass is ended.
Otherwise, a stiffener is designed at the end of the left pass. The right pass, starting at the right
end of the web section, is then completed in a fashion similar to the left pass. As a result of this
algorithm, multiple web sections within a span may create apparently illogical transverse-
stiffener spacings near the web-section boundaries. This may require some manual adjustments
of these spacings by the user.
The stiffeners are spaced to satisfy the AASHTO requirements for shear resistance specified in
AASHTO LRFD Articles 6.10.9 (I-girders) and 6.11.9 (box girders). The stiffener spacings are
limited to the maximum values specified in those articles. The stiffener spacing is determined
using the largest shear force or stress in the panel in the appropriate shear-resistance equation;
the factored sum of the shears is interpolated to determine that value. Transverse stiffeners are
conservatively spaced to the nearest 5 percent of the web depth to simplify the numerical
work; the spacings are then adjusted to the next lowest modular 3-inch increment.
All web sections, even if specified as not transversely stiffened, are passed through the
transverse-stiffener-design routine. This procedure is a check against a web that might not have
been completely checked in the design process (i.e. a web section without at least one flange or
web splice). If transverse stiffeners are unnecessary, they are not designed. It is possible that a
few transverse stiffeners may be required in a web section that the user had specified as
unstiffened. LRFD Simon prints a warning that such stiffeners have not been checked for
fatigue. The user should rerun LRFD Simon for one design cycle with that web section specified
as transversely stiffened. The converse is also true; transverse stiffeners may not be required in
a web section that the user has specified to be transversely stiffened. The user should rerun
LRFD Simon for one design cycle with that web section specified as unstiffened to ensure that
the web design will satisfy the correct shear-resistance equations for unstiffened webs.
5.3.6.2.2 Transverse Stiffener Sizing
For any web section, one stiffener size is designed - the largest required by AASHTO in that
section. If possible, the width of a transverse stiffener is made at least equal to 1/4 of the
maximum flange width in the web section considered, as specified in AASHTO LRFD Article
6.10.11.1.2. However, if a narrower flange exists within that section, LRFD Simon limits the
width of the stiffener to that flange width. Thus, the width of the stiffener may be less than 1/4
of the maximum flange width within that web section. Other requirements in AASHTO LRFD
Article 6.10.11.1.2 regarding the stiffener width and thickness are also checked by LRFD Simon.
The transverse-stiffener moment of inertia, I, required by AASHTO LRFD Article 6.10.11.1.3 is

that required for a pair of stiffeners (rather than one) if the stiffeners are on both sides of the
web. For one-sided transverse stiffeners, the moment of inertia is computed about the web
face; for two-sided stiffeners, the moment of inertia is computed about the web mid-plane.
The transverse-stiffener moment of inertia, It , required by AASHTO LRFD Equation 6.10.11.1.3-

11 for web sections with longitudinal stiffeners is that required for a pair of transverse
stiffeners (rather than one) if the stiffeners are on both sides of the web. For consistency, It and
the moment of inertia of the longitudinal stiffener, Iℓ , in AASHTO LRFD Equation 6.10.11.1.3-11
are computed at the same relative location, i.e. on the web opposite the longitudinal stiffener.
In computing Iℓ, a centrally located web strip (18tw in width) is considered by LRFD Simon.
Since the transverse stiffeners are designed in the bill-of-materials routines, any longitudinal
stiffener defined by the user is assumed to be located near the compression flange. Thus, the
web is considered to be longitudinally stiffened in designing the transverse stiffeners because
these routines do not have access to the information needed to determine if the longitudinal
stiffener is ineffective. The user should check the evaluation sections of the output to ensure
that an unsuitable longitudinal stiffener has not been detected.
Transverse stiffeners are sized to the nearest 0.25 inch in width and 0.125 inch in thickness. For
weight and cost computations, a 2-inch cutback of the transverse stiffeners is assumed.
5.3.6.3 Bearing Stiffener Design
Bearing stiffeners are designed separately for the factored reactions at each support according
to the provisions of AASHTO LRFD Article 6.10.11.2. For box girders, the bearing stiffeners are
designed as a pair of vertical plates assumed welded onto a solid-plate support diaphragm,
which for this computation is assumed to have the same thickness as the web over the support.
The diaphragm is not designed by LRFD Simon. Each box-girder support is assumed to be
supported on two bearings.
5.3.6.4 Longitudinal Web Stiffeners
The width and thickness of longitudinal web stiffeners must initially be defined by the user on
the Web Cross Section Information Form (Article 3.11.2). Both top and/or bottom longitudinal
web stiffeners can be defined in any web section. The yield strength of the longitudinal
stiffeners can also be defined on the Material Properties Form (Article 3.4).
The width of a longitudinal web stiffener is kept at the value specified by the user; the thickness
is increased during the design cycles to meet the AASHTO longitudinal-stiffener width-to-
thickness requirement specified in AASHTO LRFD Article 6.10.11.3.2. The thickness of a
longitudinal stiffener is never decreased by LRFD Simon. In checking AASHTO LRFD Equation
6.10.11.3.2-1, LRFD Simon uses the yield strength of the adjacent flange instead of the yield
strength of the longitudinal stiffener. The yield strength of the adjacent flange is conservatively
used in these requirements to prevent overstressing the stiffener if it has a lower yield strength
than the flange. The requirement is checked for both flanges, which could affect the
longitudinal stiffener adjacent to the tension flange in an unusual case; this is warranted since it
can be argued that the tension flange could possibly go into compression.
Neither static nor fatigue stresses are checked in the longitudinal web stiffeners; generally, if
the web yield strength is over 50 ksi, the longitudinal stiffeners should have a yield strength of
at least 50 ksi. Instead, the user is expected to input an appropriate longitudinal-stiffener yield
strength. AASHTO LRFD Equation 6.10.11.3.1-1 is not meaningful in LRFD Simon because the
longitudinal stiffener is proportioned for the yield strength of the adjacent flange.
The moment of inertia and radius of gyration of the longitudinal stiffener are checked in the
bill-of-materials routines against the stiffness formulas specified in AASHTO LRFD Article
6.10.11.3.3. The actual transverse-stiffener spacing is used in the stiffness formulas. The
moment of inertia and radius of gyration are computed about the centroid of a T section
formed by the longitudinal stiffener and a centrally located web strip 18tw in width, as
permitted in AASHTO LRFD Article 6.10.11.3.3. If the stiffness checks fail, a warning message is
printed and the longitudinal-stiffener thickness is increased. The design routines will not have
considered this larger size. The user should input this larger size and rerun the program since
the larger stiffener may permit a reduced flange or web thickness. If an excessive longitudinal-
stiffener thickness is obtained, the user can rerun LRFD Simon with an increased longitudinal-
stiffener width or a reduced maximum transverse-stiffener spacing.
If a web is not transversely stiffened or if the longitudinal stiffener is not adjacent to the
compression flange, the section is not considered longitudinally stiffened in the design routines;
for such cases, a warning message is printed in the evaluation portion of the output. However,
in the bill-of-materials routines, the longitudinal stiffener is assumed to be adjacent to the
compression flange in the stiffener designs. Thus, the user should check for warning messages
in the evaluation sections of the output. In areas of moment reversal, the portion of the web

opposite from the longitudinal stiffener may experience compression while not being
longitudinally stiffened. LRFD Simon prints a warning in such a case and gives the magnitude of
the compressive stress at D/5 from the compression flange. The user should consider utilizing a
longitudinal stiffener in such a region.
An excessive longitudinal-stiffener thickness may result because the transverse-stiffener

spacing governs the longitudinal-stiffener size. This condition may be acute near a haunched
support. The user can limit the maximum transverse-stiffener spacing below that set by the
AASHTO specifications on the Transverse Stiffener Properties Form (Article 3.7) and thereby
reduce this excessive thickness; this limit will probably not govern in the shallower regions of
the girder.
Transverse-stiffener size and longitudinal-stiffener size are kept constant within each web
section in LRFD Simon. However, both stiffeners are simultaneously designed for each
transverse-stiffener spacing along the web. Since AASHTO LRFD Article 6.10.11.1.3 requires a
functional relationship between the size of the two stiffeners, it is possible that an increased
longitudinal-stiffener size at a web location will not meet this relationship at a previously
checked location. LRFD Simon does not recheck this relationship, and the user should ensure
that this relationship has not been violated. LRFD Simon prints a message whenever the
longitudinal-stiffener thickness is increased. It is best to rerun LRFD Simon with that increased
longitudinal-stiffener size.
Since LRFD Simon will not reduce the size of a longitudinal stiffener and since the size of the
transverse stiffeners is related to that of the longitudinal stiffener, the user should avoid
specifying an oversized longitudinal stiffener so that oversized transverse stiffeners do not
result.
Longitudinal web stiffeners are assumed by LRFD Simon to be located a distance of D/5 from
the inner surface of the compression flange. Stresses for computing stress ranges to check the
fatigue detail at the stiffener end are computed at these locations on the web. When the
neutral axis is close to the top flange, the location of D/5 assumed by LRFD Simon may fall in
the tensile zone of the web. However, when the neutral axis is high, the amount of web in
compression is small and the longitudinal stiffener is likely to be adequate anywhere in this
region - especially since the entire web depth must be designed for a depth/thickness
requirement. It should be noted that other locations of the stiffener (i.e. other than D/5 from
the inner surface of the compression flange) may more optimally satisfy the requirements
specified for each limit state in AASHTO LRFD Article 6.10.11.3.1. Since LRFD Simon does not
allow the assumed vertical location of the longitudinal stiffener on the web to be varied, other
potentially more optimal locations on the web will need to be investigated manually by the
user.

The maximum transverse-stiffener spacing in a longitudinally stiffened web section is taken as
1.5D in LRFD Simon, as specified in AASHTO LRFD Article 6.10.9.1 (where D is the web depth).
The user should be aware that web panels with longitudinal stiffeners must include transverse
stiffeners at a spacing of 1.5D or less, whether or not they are required for shear, in order to
provide support to the longitudinal stiffeners along their length (AASHTO LRFD Article
6.10.11.1.1). LRFD Simon may not provide these stiffeners if they are not required for shear;
the user is advised to carefully cross-check all longitudinally stiffened web panels with the
transverse stiffener spacings in those panels provided in the bill of materials.
Longitudinal stiffeners are included in the section properties by LRFD Simon for checking
stresses in the design routines, but are not included for computing stiffness in the analysis
routines. For the section-property computation, LRFD Simon again assumes that a longitudinal
stiffener is located at 20 percent of the web depth from the associated flange. The user should
ensure that the stiffener is adequately attached and spliced so that it is capable of developing
the bending stresses and does not generate a fatigue crack. In including the longitudinal
stiffeners in the section properties, the assumption is made that the stiffeners are continuous,
and thus, they are not interrupted at intersections with transverse stiffeners. To evaluate a
girder with discontinuous longitudinal stiffeners, input small web sections without longitudinal
stiffeners adjacent to the actual transverse-stiffener locations. Discontinuous longitudinal
stiffeners are best avoided.
5.3.7 Shear-Connector Design
When an acceptable design has been detected by LRFD Simon, shear connectors will be
designed if the user requested such a design on the Shear Stud Properties Form (Article 3.8).
Since the shear-connector design has no effect on the girder design, an efficient procedure is to
request a shear-connector design only after the girder design is finalized.
If a composite concrete slab is specified anywhere in a span, studs are designed along the full
length of the span. A basic assumption in LRFD Simon is that if a slab is composite, it will
behave compositely over the entire span length. LRFD Simon will stop if a shear-connector
design is requested and no concrete slab is specified anywhere along the girder length.
Because studs are assumed to be effective over the full length of the span if concrete is
specified, a bridge that is non-composite over an interior support cannot be exactly designed.
By specifying a zero rebar area, an approximate design can be obtained. In computing the
fatigue stress range in this case, however, positive live-load moment stresses will be computed
using n-concrete section properties.
For an I girder, the user may specify that the studs be omitted in a region up to 5 percent of the
span on either side of each interior support to eliminate potential fatigue problems with the
stud-to-flange connections in that region (a fatigue Detail Category C). A larger length is not
permitted because this would be inconsistent with the assumption that the longitudinal
reinforcing bars are part of the cross-section in that region. For a box girder, the studs may not
be omitted in any region over an interior support, since that would be inconsistent with the
assumption that the slab acts as part of the box in providing torsional rigidity. LRFD Simon
does not compute the number of additional shear connectors required at points of
contraflexure when the rebars are not included in the computation of the section properties in
negative-moment regions; i.e., when the section is non-composite for negative flexure in the
final condition (AASHTO LRFD Article 6.10.10.3).
If a shear-connector design is requested, only Nelson-type studs are considered. The user must
indicate on the Shear Stud Properties Form (Article 3.8) the stud diameter and length, number
of studs per row, concrete unit weight, and desirable pitch increment to completely define the
design requirements. Prior to designing the shear connectors, LRFD Simon checks the stud
proportion, transverse spacing, and cover and penetration requirements specified in AASHTO
LRFD Articles 6.10.10.1.1, 6.10.10.1.3, and 6.10.10.1.4, respectively. In checking the transverse
spacing requirements, a minimum center-to-center stud spacing of 4 times the stud diameter is
assumed. The shear connectors are designed to satisfy fatigue requirements (AASHTO LRFD
Article 6.10.10.2), and are checked for ultimate-strength requirements (AASHTO LRFD Article
6.10.10.4). If additional studs are needed to satisfy the ultimate-strength requirements, the
number of additional studs that is required within each region/portion of a span is provided in
the output. Radial forces are not considered in the shear-connector design by LRFD Simon.
In the fatigue design, a check is made for the stud stressed by horizontal shear and connected
to the top flange. In the design routines, a separate check for fatigue of a flange stressed axially
with a welded stud is performed (checked against fatigue Detail Category C). These two checks
are independent. In computing the required pitch, the shear range from the analysis due to the
fatigue load (AASHTO LRFD Article 3.6.1.4) is used. (Note: in determining whether infinite life
or finite life controls in determining the nominal fatigue resistance, Zr, of an individual stud, an
(ADTT)SL value of 1,090 trucks per day is used by LRFD Simon instead of the (ADTT)SL value of
960 trucks per day currently specified in AASHTO LRFD Article 6.10.10.2. The value of 960
trucks per day will be revised to 1,090 trucks per day in the 9th Edition AASHTO LRFD
Specification to correctly reflect the updated ratio of the load factors for the Fatigue I and
Fatigue II load combinations appearing in the 8th Edition Specification).
In spacing the studs, LRFD Simon attempts to space them as far apart as possible along the
girder to keep the number of studs at a minimum. Starting at the left end of the girder, LRFD
Simon first tries a spacing of 48 inches if the web depth within the entire range under
consideration is greater than or equal to 24 inches; otherwise, a spacing of 24 inches is initially
tried (i.e., the maximum spacing allowed by AASHTO LRFD Article 6.10.10.1.2). LRFD Simon then
compares that spacing to the closest minimum required pitch for fatigue computed at the
adjacent 20th points of the span. If that spacing is greater than the required pitch, the spacing is
reduced by the desired pitch increment input by the user and the process is repeated. If the
required pitch is less than the desired pitch increment, LRFD Simon will stop the process. LRFD
Simon checks to ensure that adjacent stud shear connectors are not closer than 6 diameters

center-to-center, as specified in AASHTO LRFD Article 6.10.10.1.2. If additional rows are
needed to satisfy the ultimate-strength requirements, they are inserted between each row
required to satisfy the fatigue requirements. If additional rows are still needed, the resulting
rows are subdivided again until as many rows as needed are inserted. In some cases, this may
result in pitches that are less than the specified minimum pitch. The resulting pitch (in inches),
number of spaces, and associated range length (in feet) is output for each span immediately
after the bill of materials.
For a box girder, the effect of an inclined web on the horizontal shear force applied to the studs
is considered by using the web in-plane shear force in the standard VQ/I computation.
In the stud ultimate strength check, any longitudinal web stiffeners are included in the ultimate
force of the steel section. If the maximum moment is located within 10 percent of the span
end, the stud ultimate strength is not checked for that span.
5.3.8 Field Splice Design Information (for NSBA Splice)
When an acceptable design has been detected by LRFD Simon, design information is tabulated
at each field splice location entered by the user on the Field Splice Cross Section Information
Form (Article 3.11.6). This design information is provided immediately following the shear
connector design report, or after the bill of materials if a shear connector design is not
requested by the user.
This information is provided as a convenience to assist the user with the entering of the
necessary data into the separate NSBA Splice design spreadsheet (for more information on
NSBA Splice, please visit the NSBA homepage www.steelbridges.org) for the design of the
bolted field splice at each location. Data provided at each field splice location include the
unfactored moments and shears at the centerline of the splice, girder properties for the
sections immediately to the left and right of the splice, and additional miscellaneous available
information needed by the NSBA Splice design spreadsheet.
5.3.9 Fatigue Design
5.3.9.1 General
Details are checked by LRFD Simon for either the Fatigue I or Fatigue II load combination
depending on the fatigue detail category and the single lane average-daily truck traffic, (ADTT)SL
(see AASHTO LRFD Table 6.6.1.2.3-2), that is input by the user on the General Properties Form
(Article 3.2). The appropriate adjustments are made to the (ADTT)SL values given in AASHTO
LRFD Table 6.6.1.2.3-2, as necessary, for the fatigue service life entered by the user on the
General Properties Form (see AASHTO LRFD Article C6.6.1.2.3). Eq. C6.6.1.2.3-1 is used directly
in this case to make the necessary adjustments. The unfactored dead load stress is also
computed and is used by LRFD Simon to determine whether or not the detail under

consideration is subject to a net tensile stress under the sum of the stresses due to the
unfactored dead loads and the Fatigue I load combination indicating that fatigue must be
checked (see AASHTO LRFD Article 6.6.1.2.1). If the component is always in compression under
this sum, fatigue is not checked by LRFD Simon. Live load stress ranges are computed by LRFD
Simon for both the Fatigue I (load factor = 1.75) and Fatigue II (load factor = 0.80) load
combinations. Further information on the computation of these stress ranges is provided in
Article 5.3.2.3.
LRFD Simon also checks the special fatigue requirement for webs specified in AASHTO LRFD
Article 6.10.5.3 using the total shear due to the unfactored dead load plus the shear due to the
Fatigue I load combination. These shears are output in the last two columns of the Detailed
Information table for each section under ′FATIGUE I′ and are highlighted with asterisks. LRFD
Simon makes this check for both homogeneous and hybrid sections with unstiffened or
stiffened webs.
LRFD Simon designs a single girder and considers many details related to a single girder in the
fatigue design. However, a bridge is composed of two or more girders structurally connected;
many of the details in these connections are not considered in LRFD Simon. So that a user will
be clear as to which common girder details are considered by LRFD Simon and which aren't,
these details are grouped and discussed below. A category in parenthesis following a detail
refers to the AASHTO fatigue detail category from AASHTO LRFD Table 6.6.1.2.3-1, assumed by
LRFD Simon to be appropriate for that detail.
5.3.9.2 Details Checked and Redesigned
1. Flange base metal - If painted steel is specified by the user on the Material Properties Form
(Article 3.4), the appropriate nominal fatigue resistance for Detail Category A is used in this
check. If uncoated weathering steel is specified by the user on the Material Properties
Form, the appropriate nominal fatigue resistance for Detail Category B is used in this check.
This check is only made at non-splice locations.
2. Groove-welded or slip-resistant bolted splice in a flange (Detail Category B) - In reference to

the flange material; bolt patterns and splice plates are not considered. For AASHTO M270
Grade 100/100W material adjacent to a groove-welded splice, see No. 9.
3. Web-flange fillet weld (Detail Category B).
4. Fillet- or groove-welded connection of full-depth cross-frame connection plates to the

inside surface of a flange (Detail Category C′) – LRFD Simon assumes that this detail exists at
each section checked, unless bolted connections are specified by the user on the Material
Properties Form (Article 3.4) - see No. 5. This check can be disregarded if a connection plate
does not actually exist at a section. To ensure that this check is made at the actual
connection-plate locations, define a web-section range to each connection plate in a span.
5. Bolted connection of full-depth cross-frame connection plates to the inside surface of a
flange (Detail Category B) - If specified by the user on the Material Properties Form (Article
3.4), LRFD Simon assumes that this detail exists at each section checked; otherwise, a
welded connection is assumed (see No. 4). This check can be disregarded if a connection
plate does not actually exist at a section. To ensure that this check is made at the actual
connection-plate locations, define a web-section range to each connection plate in a span.
6. Termination of the vertical fillet weld at a location near the inside surface of a flange
connecting an intermediate transverse stiffener or a full-depth cross-frame connection
plate to the web (Detail Category C′) - Near the flange is defined in LRFD Simon as 2½" from
the nearest flange for web thicknesses less than or equal to ½" and 3¼" from the nearest
flange for web thicknesses greater than ½". LRFD Simon assumes that this detail exists at
each section checked. This check is made if connection plates are welded or bolted to the
flange. This check can be disregarded if a stiffener or connection plate does not actually
exist at a section.
7. Top flange with Nelson-type stud (Detail Category C) - In the stud design, fatigue of a stud
due to horizontal shear is also considered (Article 5.3.7).
8. Rebar (AASHTO LRFD Article 5.5.3.2) - If the performance ratio for rebar fatigue exceeds the
maximum acceptable ratio, the top-flange thickness is increased and the design continues.
9. AASHTO M270 Grade 100/100W base metal and weld metal in or adjacent to a groove-
welded splice (Detail Category B') - If another steel is used on one side of the splice, the
output fatigue performance ratio for the splice must be multiplied by the ratio of the
appropriate nominal fatigue resistance for Detail Category B to the nominal fatigue
resistance for Detail Category B' to determine the correct fatigue performance ratio for that
side of the splice.
LRFD Simon assumes that all butt welds are full-penetration groove welds with any backing bars
removed and that all web-flange welds are continuous fillet welds. These welds are checked by
LRFD Simon under fatigue Detail Category B. If continuous partial- penetration groove welds are
used, or if continuous full-penetration groove welds are used without removing any backing
bars, a separate hand calculation must be made to check these welds for fatigue Detail
Category B'.
5.3.9.3 Details Checked and Not Redesigned but Warning Printed
1. Termination of longitudinal web stiffener (Detail Category E or E') – Detail Category E is

checked when the longitudinal stiffener is less than 1.0 inch in thickness. For stiffeners
greater than or equal to 1.0 inch in thickness, Detail Category E' is checked. The user is
cautioned that if the thickness of the longitudinal web stiffener is increased to 1.0 in. or
greater to meet rigidity requirements in the bill-of-materials routines, a separate hand
calculation should be made to check the termination against fatigue Detail Category E', or
else LRFD Simon should be rerun for one design cycle with the increased longitudinal-
stiffener size.
2. Termination of bottom-flange tee longitudinal stiffener in a box girder (Detail Category E or

E′) - At a bottom-flange splice of a box girder, if a flange longitudinal stiffener exists on
either or both sides of the splice, LRFD Simon will check for fatigue at the stem of the
stiffener. The user may reduce the stress concentration at the end of the stiffener by
including a splice in the stiffener. A warning message is printed by LRFD Simon when the
computed performance ratio is over the maximum acceptable ratio at the stiffener
terminations, but no redesign is performed. LRFD Simon does not know the actual detail of
these stiffener terminations and therefore must assume a Category E or E' detail. If these
warnings are printed, one option for the user is to specify in the actual bridge a detail with a
higher nominal fatigue resistance (see AASHTO LRFD Table 6.6.1.2.3 – Condition 4.3). A
particular detail may be checked without rerunning LRFD Simon by multiplying the
performance ratio for Category E or E' by the ratio of the nominal fatigue resistance of the
higher nominal fatigue resistance detail and that for Category E or E'; if the resulting
number is below 1.0, the higher nominal fatigue resistance detail meets the AASHTO LRFD
specification. Since these details can often be expensive to fabricate, an alternative
suggestion is to extend the Category E or E' stiffener detail into a region of lower stress
range or into a region of compressive stress only. Either alternative would require rerunning
LRFD Simon.
5.3.9.4 Details Not Checked
1. Lateral-bracing connections and gusset plates.

2. Diaphragm connections and gusset plates.
3. Floor-beam connections and gusset plates.
4. Hinge detail and related plates.
5. Miscellaneous attachments and any detail not mentioned above.
If details not checked by LRFD Simon are used, the output from LRFD Simon may still be useful.
Details that are checked can be used to estimate the fatigue resistance of details not checked.
One way is discussed above. Another way would be to make use of the knowledge that a
section checked in a girder with full-depth cross-frame connection plates that are welded to the
flanges must meet Category C′ between the flanges because of the connection-plate welds at
the flanges. Thus, any other Category C′ detail (or detail with a higher nominal fatigue
resistance) is also acceptable between the flanges at that section.

5.3.10 Lateral-Torsional Buckling
In LRFD Simon, lateral-torsional buckling between cross-frames is checked for the following
cases:
 The bottom flange of the non-composite I-girder in regions of negative bending under
the DC1 loads before the concrete deck has hardened (for constructibility);
 The bottom flange of a composite or non-composite I-girder in regions of negative
bending under the total factored loads after the concrete deck has hardened (at the
strength limit state);
 The top-flange of the non-composite I-girder, or the top flanges of the non-composite
box girder, in regions of positive bending under the DC1 loads plus any construction
lateral moment before the concrete deck has hardened (for constructibility and the deck
pours) if the user indicates that the top flange is not fully braced for non-composite
loads on the Span Information Form (Article 3.10.7);
 The top flange of an I-girder, or the top flanges of a box girder, in regions of positive
bending under the total factored loads after the concrete deck has hardened (at the
strength limit state) if the user indicates that the top flange is not fully braced for the
final state on the Span Information Form (Article 3.10.7).
The lateral-torsional buckling resistance is always computed using the appropriate

corresponding cross-frame spacing entered by the user on the Span Information Form (Articles
3.10.6 and 3.10.7).
The moment gradient modifier, Cb, is always calculated by LRFD Simon as specified in AASHTO
LRFD Article 6.10.8.2.3 (see also AASHTO LRFD Article C6.4.10). As discussed in a User Note in
Article 3.10.7, if the user-input cross-frame spacing does not divide a span into a whole number
of uniform unbraced lengths, LRFD Simon computes cross-frame spacing for the flange that
divides the entire span evenly. This adjusted uniform spacing is output on the first design cycle.
When this adjustment is made, the factored stresses at the adjusted cross-frame locations
(instead of at the locations based on the user-input cross-frame spacing) are used in the
computation of Cb for the unbraced length under consideration. The computed value of Cb is
given in the Detailed Information Table at each section.
In cases where the computed value of Cb is greater than 1.0, LRFD Simon currently does not
compute the lateral-torsional buckling resistance using the equations specified in AASHTO LRFD
D6.4.1; the equations given in AASHTO LRFD Article 6.10.8.2.3 are always used.
For unbraced lengths containing a transition to a smaller section at a distance less than or equal
to 20 percent of the unbraced length from the brace point with the smaller moment (Exhibit
51), LRFD Simon determines the lateral-torsional buckling resistance assuming the transition to
the smaller section does not exist (i.e. using the larger section along the unbraced length and

the computed value of Cb assuming a prismatic section – see AASHTO LRFD Article 6.10.8.2.3).
The user must ensure in this case that the lateral moment of inertia of the flange or flanges of
the smaller section is equal to or larger than one-half the corresponding value in the larger
section.
• If L2 ≤ 0.20Lb and Iy2 ≥

0.5Iy1, then ignore
transition and may
use K & Cb ≠ 1.0
2 1
• Otherwise, compute
L2 L1
Fnc using smaller
Lb
section; Cb = 1.0 and
K = 1.0 CL CL
Cross-Frame Pier
Girder Elevation
Exhibit 51: Unbraced Length Adjacent to a Pier with a Single Section Transition.
For unbraced lengths containing a transition to a smaller section at a distance greater than 20
percent of the unbraced length from the brace point with the smaller moment, LRFD Simon
determines the lateral-torsional buckling resistance as the smallest resistance within the
unbraced length assuming the unbraced length is prismatic. In addition, Cb is always taken
equal to 1.0 in this case (see AASHTO LRFD Article 6.10.8.2.3 and Exhibit 51).
For a case with more than one transition within the unbraced length, any transition located
within 20 percent of the unbraced length from the brace point with the smaller moment is
ignored by LRFD Simon, and the lateral-torsional buckling resistance of the remaining
nonprismatic unbraced length is computed as the smallest resistance based on the remaining
sections (with Cb taken equal to 1.0).
In cases where the cross-frame has been adjusted to provide a uniform spacing (see above), the
determination of whether or not the section is prismatic or non-prismatic (i.e. using the 20
percent rule) is based on the adjusted spacing.
To avoid a significant reduction in the lateral-torsional buckling resistance, the user should
consider locating flange transitions within 20 percent of the unbraced length from the brace
point with the smaller moment (with the lateral moment of inertia of the flange or flanges of
the smaller section equal to or larger than one-half of the corresponding value(s) in the larger
section).
LRFD Simon currently checks lateral-torsional buckling using the factored compressive bending
stress at the section under consideration, rather than the largest factored compressive bending
stress within the unbraced length as specified in AASHTO LRFD Article 6.10.1.6.

5.3.11 Hinged Bridges
For a hinged bridge:
A. If the negative-moment lateral-bracing spacing is larger than the hinge-to-pier distance,

the program prints a message and aborts. LRFD Simon assumes that both sides of a
hinge are laterally braced.
B. If a section is located within the nearest three span tenth points of a hinge, the moment
is linearly interpolated between the tenth-point ordinates because the moment
envelope is discontinuous at the hinge. The shear envelope is not discontinuous at a
hinge, so parabolic interpolation between the tenth-point ordinates is used.
C. LRFD Simon does not design or check hinge details. The user must ensure that a hinge
can adequately transmit the design shear without exceeding permissible stresses and
stress ranges. However, LRFD Simon does check a section at a hinge.
D. LRFD Simon assumes that any longitudinal web stiffener at a hinge is adequate to brace
the web against buckling on that side of the hinge because the zero-moment condition
causes the compression flange to be undefined.
E. The transverse-stiffener spacing at hinges may not satisfy the requirements of AASHTO
LRFD Article 6.10.9; LRFD Simon prints a warning message in the bill of materials.
F. LRFD Simon assumes that the AASHTO live-load deflection requirement for a cantilever
is inappropriate at a hinge. Live-load deflection is checked the same as for an unhinged
span.
G. The user must ensure that an input structure is stable and be aware that an unstable
structure may still generate a design.
5.3.12 Reactions
LRFD Simon outputs unfactored dead and live load plus impact reactions at each support.
Dead load reactions due to the weight of the girder, other DC1 loads, DC2 loads (composite dead
loads), utility loads and the future wearing surface (FWS) are provided.
Live load plus impact reactions are provided for the HL-93 design live load, for the user-
designed design vehicle (if specified), and for the fatigue live load. The envelope reactions for
the HL-93 design live load and user-defined design vehicle are also provided. In each case,
maximum and minimum vehicle reactions are provided (which represent the truck and lane
reactions combined), which include the dynamic load allowance and distribution factors.
These reactions can be used for the design of the bearings. Maximum and minimum truck and
maximum and minimum lane reactions are also provided for each case. These reactions do not

include the dynamic load allowance or the distribution factors, and can be used to assist the
user with the design of certain substructure elements.
Negative dead and live load plus impact reactions indicate uplift. The user should appropriately
combine the dead and live load reactions in such cases to check for uplift at end supports. Note
that if LRFD Simon is used for the preliminary design of horizontally curved or straight skewed
bridges, uplift that might be detected in a more refined analysis may not be detected by LRFD
Simon.

6 PROGRAM LIMITATIONS
To reiterate what is stated in the Introduction (Article 1), the LRFD Simon results are most
applicable and accurate for the design of tangent I- and box-girder bridges with limited or no
skew. With experience and by making some rational and proper assumptions, the program can
also potentially be used to prepare reasonable approximate preliminary starting trial girder
designs for horizontally curved bridges and straight bridges with more significant skew for input
into more refined analysis programs. It is not recommended that the LRFD Simon results be
used for the final design of those types of bridges.
The following is a list of the current limitations of LRFD Simon. The list contains the most
significant limitations and is not necessarily exhaustive:
 The rigid cross-section equation (AASHTO LRFD Eq. C4.6.2.2.2d-1) is not considered in
the Program Defined Distribution Factors for exterior I-girders for moment or shear.
 No wind loads, thermal loads or braking loads are considered.
 The STRENGTH III, STRENGTH IV and STRENGTH V load combinations are not considered.
 Flange lateral bending stresses are not considered at the service, fatigue or strength
limit states.
 Accumulated factored stresses in the deck slab that is assumed hardened for deck pours
subsequent to previously placed deck pours at a section are not provided (to help the
user determine where to cut off the minimum one-percent longitudinal reinforcement
in the deck for the deck pouring sequence). Accumulated factored stresses in the steel
girder due to the deck pours are currently calculated using the properties of the steel
section only.
 Deflections and reactions due to the deck pours are not provided.
 The global displacement amplification provisions of AASHTO LRFD Article 6.10.3.4.2 for
slender I-girder bridge units with two or three girders are not considered for the deck
pours.
 Lateral-torsional buckling is currently checked using the factored compressive bending

stress at the section under consideration, rather than the largest factored compressive
bending stress within the unbraced length as specified in AASHTO LRFD Article 6.10.1.6.
The largest performance ratio reported within the unbraced length is the one that
actually applies to the entire unbraced length. Also, in cases where the computed value
of Cb is greater than 1.0, LRFD Simon currently does not compute the lateral-torsional
PROGRAM LIMITATIONS 143
buckling resistance using the equations specified in AASHTO LRFD D6.4.1; the equations
given in AASHTO LRFD Article 6.10.8.2.3 are always used.
 The provisions of Article 6.10.1.8 are not considered in their entirety at defined field
splice locations (LRFD Simon assumes there are holes in the tension flange at these
locations to accommodate a bolted field splice). LRFD Simon does check the factored
tensile stress on the gross area of the flange, ft, against the specified minimum yield
strength of the flange, Fy. However, LRFD Simon does not check ft against the value,
0.84(An/Ag)Fu (refer to AASHTO LRFD Eq. 6.10.1.8-1). Instead, the minimum required
An/Ag ratio to satisfy AASHTO LRFD Eq. 6.10.1.8-1 when the bottom flange is subject to
tension at a defined field splice location is provided in the output.
 The provisions of Article 6.10.10.3 (special shear connector requirements for points of
permanent load contraflexure) are not considered. Radial forces are not considered in
the design of the shear connectors.
 The optional provisions of Appendix A6 are not considered for composite I-sections in
negative flexure and non-composite I-sections with compact or noncompact webs.
Rolled sections can be input as equivalent welded girder sections in LRFD Simon;
however, the sections will be conservatively designed as slender-web sections.
 The optional moment redistribution provisions of Appendix B6 are not considered.
 The provisions of Article D6.5 (web local yielding and web crippling) are not considered.
 The option to include J in calculating the lateral torsional buckling resistance of sections
with non-slender webs for constructibility checks (Article C6.10.3.2.1) is not considered.
 The assumed vertical location of a longitudinal web stiffener is fixed at D/5 from the
inside face of the compression flange, and cannot be changed.
 For a linear or parabolic haunch, the inclined nature of the lower-flange force is not
considered in the flange stress or shear computations.
The entire AASHTO LRFD Specification must be considered by the Engineer responsible for the
design.
144 PROGRAM LIMITATIONS

APPENDIX A: QUICK INSTALLATION GUIDE
APPENDIX A: QUICK INSTALLATION GUIDE 145

Before you Begin
You must be logged on with Administrator rights when installing or uninstalling this product on
operating systems that provide user privileges (e.g. Windows Vista, Windows 7, etc.).
On some systems, successful installation may require that you update your system with the
latest Windows operating system DLLs. We recommend that you update your system
periodically, particularly if you experience problems.
You should uninstall any previous Beta version of LRFD Simon prior to installing any newer
version. You can uninstall previous versions using the Windows “Add or remove program” or
“Uninstall a program” (this will vary depending on the version of Windows you are running).
You may be requested to reboot your system during the installation process. Although you have
the option of rebooting at a later time, we recommend that you allow the installation program
to reboot your system if and when you are prompted.
NOTE: Should your system be rebooted during the installation process, you must log back in
after the reboot to the same account and with the same Administrative rights used for the
installation process so it can complete properly.
It is highly recommended that you close any programs or processes that are running before you
start the installation program for this product.
Software Prerequisites
LRFD Simon requires that prerequisites be installed before its installation. These are merely an
installation sequence of various Microsoft packages that must be in place before LRFD Simon
will install and run correctly. In most cases these will already be available if you are running
Windows 7 or later; however there may be instances with older operating systems such as
Windows XP where this is not the case.
The LRFD Simon Software Prerequisite:
Microsoft .NET Framework 4.0 (Client):

http://www.microsoft.com/download/en/details.aspx?id=17113
The LRFD Simon installer will alert you if the prerequisite has not been met. If you are running
Windows XP you should ensure that you have Service Pack 2 or later installed.
146 APPENDIX A: QUICK INSTALLATION GUIDE

Installing LRFD Simon
The installation wizard will then lead you through the installation process; note that during the
installation you should read and must accept the terms of the end user license agreement
(EULA). An option is available to print the EULA on the installation screen (Error! Reference
source not found.). If you press the “No” button, meaning that you do not accept the terms of
the EULA, the Install Wizard will exit and the program will not be installed.
Exhibit 52: Installation End User License Agreement (EULA) Screen.
NOTE: At any time should you want to end the installation before the program is fully installed,
you can press the “Cancel” button.
Following the acceptance of the EULA, you will then be prompted to review and modify the
location of the LRFD Simon application files if necessary (Exhibit 53). By default, the program
files will be installed in your “Program Files (x86)” folder. It is rarely necessary to and not
recommended that you change this default location. However, if you would like to change the
location where the program files are installed, you can press the “Browse…” button and select a
new folder location. If you are satisfied with the folder location for the application files, you
can press the “Next >” button and proceed to the next step.

Exhibit 53: Installation Application Files Destination Location Screen.
After accepting the destination folder for the application files, the next screen will allow you to
choose the destination folder for the sample input files (Exhibit 54). By default, the sample
input files will be installed to your Windows Documents folder “LRFD Simon (AASHTO 8th
Edition) Models”. Depending on the user account used to install LRFD Simon, the root location
will vary. If you would like the sample input files to be accessible by all users, you should
change the destination location to a folder that is accessible by all users. Changing the
destination location can be accomplished by pressing the “Browse…” and selecting a new
folder. If you are satisfied with the folder location for the sample input files, you can press the
“Next >” button and proceed to the next step.
Exhibit 54: Installation Sample Input File Destination Location Screen.

Once the destination location for the sample input files has been accepted, the Installation
Wizard will then allow you to select the Program Folder where the application shortcuts will be
located (Exhibit 55). By default, the program folder will be defined as “NSBA LRFD Simon”.
However, if you would like to change the folder name, you can enter a new name in the
“Program Folder:” text box. If you are satisfied with the program folder name you can press the
“Next >” button and proceed to the next step.
Exhibit 55: Installation Program Folder Selection Screen.
The Installation Wizard will give you an opportunity to review the settings prior to completing
the installation (Exhibit 56). If you are satisfied with the current settings, you can proceed to
complete the installation by pressing the “Next” button. Otherwise, if you would like to modify
any of the settings, you can navigate backwards to the appropriate screen using the “Back”
button.

Exhibit 56: Installation Settings Summary Screen.
Once the installation has completed successfully, you can then press the “Finish” button and
close the Installation Wizard (Exhibit 57). At this point, all of the necessary program and
example files have been installed and the Windows start menu has been updated with the
application and documentation shortcuts.
Exhibit 57: Installation Complete Screen.
Windows Start Menu and Application Shortcut

When the installation has completed, you will find a new folder added to your Windows Start
menu under "Start>All Programs>NSBA LRFD Simon". A shortcut for the User Interface
application “LRFD Simon (AASHTO 8th Edition)” and this User’s Guide will be located in this
folder.

Sample Input Files
Several example files are delivered and installed with LRFD Simon. These will allow you to
familiarize yourself with the input file format and also running the application. These examples,
by default, will be installed to your Windows Documents folder “LRFD Simon (AASHTO 8th
Edition) Models”. See Article 2.2.2.2.1 - 2.2.2.2.1Sample Input Files for more information
regarding the delivered sample input files.
NOTE: If you have multiple user accounts associated with a single computer and you would like
each user to be able to access the sample input files, you should make sure that you choose a
location that is accessible to all accounts on the machine you are installing LRFD Simon to.
Questions and Defect Reporting

Please report any defects/bugs you encounter either installing or using this version of LRFD
Simon by contacting nsbasimon@steelbridges.org. Include a description of the issue along with
steps-by-step instructions on how to reproduce the issue. Also, make sure to include the any
related LRFD Simon input file(s).

APPENDIX B – REVISION HISTORY
152 APPENDIX B – REVISION HISTORY

Summary of May 2018 Revisions - Version 10.3.0.0 (AASHTO 8th Edition)
Since the release of LRFD Simon Version 10.2.2.0 several revision requests and user requested
enhancements have been received. This release of LRFD Simon Version 10.3.0.0 (AASHTO 8th
Edition) contains the following revisions and enhancements.
Input Revisions
1. An input consistency check has been added to warn the user if a field splice has been
specified within 5% of the span length of a support (NSBA044).
2. Input consistency checks have been added to make sure that the start and end locations
of a deck pour are different, that the start location is to the left of the end location, and
that pours in the same span do not overap (NSBA045).
3. All of the example input files were reviewed to select a value for "Distribution Factor
Definition" (NSBA049).
4. An input consistency check has been added to make sure that "End Location" values
defined on the Cross Section input item are all greater than zero (NSBA051).
5. When creating the Best Design input files, the "Frequency of Cycles" input file is now
written as an integer rather than a real value for compatibility with the input
consistency checks (NSBA052).
6. "Sanity Check" warnings have removed from the input consistency checks and the
option to skip sanity checks has been removed from the program input. All input values
that were previously subject to sanity checks now have hard-coded lower and upper
limits in the GUI that ensure the user cannot enter values less than or greater than the
previous "Sanity Check" limits. Also, the messages indicating that no input checks were
violated on each command have been removed. Only failed input checks will now
appear on the consistency check list (NSBA053).
7. In the Best Design input files for box girders, if "Minimum Tee Area" and/or "Maximum
Tee Area" are left blank in the original input file, they will be left blank in the Best Design
files, as well. Previously these values were set to 0.00 in the Best Design files, causing
errors to occur in the input consistency checks (NSBA054).
Output Revisions
1. Dead and live load reaction output is now reported by support number rather than
abutment or pier number (which was incorrect for symmetrical girders) (NSBA042).
2. The transformed XML output now reports the correct bottom flange dimensions in the
field splice output (NSBA043).
Installation Related Revisions
1. The program installation has been revised to address several comments about the
content and format of the installation (NSBA046, NSBA050).
2. A revised license file has been included that extends the expiration date of program and
revises the NSBA mailing address (NSBA047).
APPENDIX B – REVISION HISTORY 153

Summary of October 2017 Revisions - Version 10.2.1.0
enhancements have been received. This release of LRFD Simon Version 10.2.1.0 contains the
following revisions and enhancements.
Input Revisions
1. The GUI now performs an input verification check when opening input files, before
running the analysis engine, and on demand from the users (Revision NSBA034).
Output Revisions
1. After a successful design run, the program now generates an input file containing the
web and flange dimensions of the best design (Revision NSBA035).
Specification Related Revisions
1. The specification checks are now consistent with the AASHTO LRFD 8th Edition
Specifications (Revision NSBA033).

Summary of March 2015 Revisions - Version 10.2.0.0
Output Revisions
1. The flange tensile strength (Fu) is now reported correctly in the program output
(Revision NSBA2014.22).
1. The live load deflection check now uses proper values for live load deflection in each
span (Revision NSBA2014.23).
2. Several small corrections were made to the calculation of the moment gradient factor,
Cb, for use with lateral torsional buckling calculations (Revision NSBA2014.26).
3. The dual tandem combination of the HL-93 live load is not considered for WisDOT users
of the program. For all other users, the program still considers the dual tandems when
reporting live load results (Revision NSBA2014.29).
4. When computing ratings for the WisDOT version of the program, the "Semi" and "PUP"
vehicles will only have single lane distribution factors applied to them. (Revision
NSBA2014.31).
User's Guide Revisions
1. Information regarding the assumptions made and methods used in the calculation of
live load distribution factors has been added to the "Program Methodologies" portion of
the User's Guide (Revision NSBA2014.30).
GUI Revisions
1. The user input "Print Rating Output" on the "Result Controls" form will now populate
properly when opening an input file. This input value is only visible to WisDOT users

Summary of February 2015 Revisions - Version 10.1.1.14
Output Revisions
1. The transformed program output has been revised to include information about shear
connectors that was previously missing (Revision NSBA2014.19).
2. The moment gradient factor, Cb, has been added to the detailed section output for
sections with discretely braced compression flanges. For sections with continuously
braced compression flanges and box girders in negative bending, this value will print as
"N/A" (Revision NSBA2014.20.4).
3. The transformed output for transverse stiffeners has been condensed into a tabular
format (Revision NSBA2014.21).
1. The second order lateral stress amplification factor is no longer incorrectly applied to
tension flanges (Revision NSBA2014.20.1).
2. The deck slab stresses are now computed with the proper section modulus and divided
by the appropriate modular ratio (Revision NSBA2014.20.2).
3. The depth of web in compression (Dc) for section in negative flexure is now calculated
only with the section consisting of the steel girder plus reinforcement (Revision
NSBA2014.20.3).

Summary of February 2015 Revisions - Version 10.1.1.13
Output Revisions
1. Several messages regarding good and bad design trials have been added to the XML and
XSLT files so they will appear in the GUI output window. These messages had previously
appeared only in the OUT file. Also, a check has been added to ensure that the designed
web thickness does not go below D/150 (or D/300 for longitudinally stiffened sections
2. The XML data for the "Detailed Information" output table for deck pours has been
revised to match the output for the limit states rows in the table (Revision
NSBA2014.16.4).
3. The XSLT file for the section properties has been revised to properly display the heading
for the "Plate+3n" column name in the Section Properties output table (Revision
NSBA2014.16.5).
4. The stresses in the deck for deck pours will now print out as "N/A" since the deck pour
checks are intended for the bare steel section only (Revision NSBA2014.16.9).
5. The composite section properties for the strength limit states (Plate + n Slab and Plate +
3n Slab) will now print as N/A for sections in negative bending, since they are never
used for strength checks in negative bending (Revision NSBA2014.16.10).
6. The section property output table has been moved before of the factored stress output.
This is a more natural progression of the program output (Revision NSBA2014.16.11).
7. The maximum and minimum shears are now reported in the program output, rather
than only reporting the maximum shear for a given limit state (Revision
NSBA2014.16.12).
8. In the section property output table the "Section Modulus to Top of Slab" now prints as
"N/A" for the "Plate + Rebar" case (Revision NSBA2014.16.13).
Program Input Revisions
1. The program has been revised to prevent a crash when the user inputs vertical webs for
a box girder (Revision NSBA2014.14).
2. The program has been revised to allow the user to enter a box girder with sloping webs
and varying web depth. It should be noted that the program does NOT maintain a
constant distance between the top flanges for this case. The user must enter varying
bottom flange widths to maintain the top flange distance, if desired (Revision
NSBA2014.15)
1. The program has been revised to use the short-term composite section properties to
compute the stresses in the slab for negative bending (Revision NSBA2014.16.6).

2. Several issues regarding the calculation of distribution factors for skewed beams and
box beams have been resolved (Revision NSBA2014.17).
Programming Revisions
1. The program has been revised to correctly handle model files that have multiple periods
in their filenames (Revision NSBA2014.13).
2. Several checks have been added to ensure a valid model file is being read into LRFD
Simon. Also, the distribution factor input form has been rearranged, and a dropdown to
specify the calculation type has been added (Revision NSBA2014.18).

Summary of September 2014 Revisions - Version 10.1.1.12
User Interface Revisions
1. An unhandled exception when entering data in the grid for the User Defined Design
Vehicle has been resolved (Revision NSBA2014.11).

Summary of August 2014 Revisions - Version 10.1.1.11 (AASHTO 7th Edition)
enhancements have been received. This release of LRFD Simon Version 10.1.1.11 (AASHTO 7th
Edition) contains the following revisions and enhancements.
Output Revisions
1. Longitudinal slab stresses are now reported at the top of slab, rather than the mid-
depth (Revision NSBA2014.1.1).
2. Formatted output showing input values for the NSBA Splice program is now provided at
the end of the program output. All values that are available from LRFD Simon are
provided. Values that are not available from LRFD Simon are indicated by "Not
available" (Revision NSBA2014.2).
3. Several inconsistencies with the programs XML and XSLT files have been corrected,
including the output table for live load reactions, the deflection units at hinge locations
and the applicability of several values on the "Detailed Information" output at each
analysis point (Revisions NSBA2014.3.1, 3.2 and 3.3).
4. When the input value "Frequency of cycles after which results are printed" is left blank,
the program now correctly prints the first and last cycles only (Revision NSBA2014.7.4).
5. Program SAN (sanity) sanity output files are now deleted at the beginning of every run
so that out-of-date files are not left around to cause confusion (Revision NSBA2014.7.7).
6. The XML and XSL output will correctly output the specification checks for Article
6.10.1.8 and also indicate the limit state they are reporting (NSBA2014.7.17).
1. The input for the slab meeting the Article 6.10.1.7 criteria for being effective in negative
bending has been moved to the Material Properties input form. This input is now
specified for the entire length of the girder rather than per slab region. If an older model
file is opened that specified the slab as meeting the 6.10.1.7 criteria, a warning will
appear and the user must visit the Material Properties input form and select an
appropriate input value. This value will also now correctly persist between design cycles
(Revisions NSBA2014.1.2 and 7.16).
2. The program will no longer recompute brace spacings for the purpose of determining if
an unbraced length exceeds a given limit. It will still use recomputed brace spacings for
the determination of brace locations for calculation of values like Cb which require
flange stresses at specific locations. if the user input brace spacing does not divide
equally. To avoid inconsistencies, the user should always enter a brace spacing that
divides equally into the current span length (Revision NSBA2014.7.2).
3. The user can no longer specify a specific number of longitudinal stiffeners for the
bottom flange of a box girder. They can choose up to 1, 2 or 3 stiffeners for the flange
via a pull down on the Box Girder Properties input form (Revision NSBA2014.7.3).
4. The transverse stiffener spacing is now defaulting to D/2 when left blank as stated in the
program User's Guide. It was previously defaulting to 24" when left blank (Revision
NSBA2014.7.5).

5. The user will no longer be permitted to save the input file while the cursor is in an input field
with a value that is above or below the input limits. Previously, this could cause the user to end
up in a validation loop (Revision NSBA2014.7.9).

1. The fatigue stress ranges are now computed without including unfactored dead load. In
addition, the fatigue output has been revised to show the fatigue range as well as the
stress in the top and bottom flanges including unfactored dead load to determine
whether a detail need be checked for fatigue requirements (Revision NSBA2014.1.3)
2. The program has been updated to comply with the 7th Edition of the LRFD
Specifications (2014) (Revision NSBA2014.4).
3. When designing box girders, the program will now honor the input for box girder
bottom flange thickness (previously, the program only used the minimum plate
thickness input from the General Properties input form) (Revision NSBA2014.6.1).
4. The program will now check lateral torsional buckling of the top flange of box girders
with sloped webs. Previously, the program would stop when a box girder with sloping
webs was specified with a discretely braced top flange (Revision NSBA2014.6.2).
5. The dual tandem case of the HL-93 live load is now correctly applied in negative
moment regions (Revisions NSBA20147.12 and 7.13).
6. During a design run, if the ductility check (AASHTO LRFD Article 6.10.7.3) fails, the
compression flange thickness will be increased. Previously, the tension flange thickness
was increased, causing the design to "run away" in some instances (Revisions
NSBA2014.7.14 and 7.15).

Summary of July 2014 Revisions - Version 10.1.1.10
1. The GUI and engine are now compiled with Visual Studio 2012, Update 4. The GUI is
compiled with the .NET Framework 4 Client Profile. The engine is compiled with the Intel
FORTRAN Composer XE 2013, SP1, Update 1 (Revision NSBA2014.10).
1. Program input has been added to allow the user to perform web depth optimization
1. The GUI and engine are now compiled with Visual Studio 2012, Update 4. The GUI is
compiled with the .NET Framework 4 Client Profile. The engine is compiled with the Intel
FORTRAN Composer XE 2013, SP1, Update 1 (Revision NSBA2014.10).
1. Program input has been added to allow the user to perform web depth optimization

Summary of October 2013 Revisions - Version 10.1.1.9
1. The program has been updated to comply with the 6th Edition of the LRFD
Specificiations with the 2013 Interims (Revision 011).
1. Program input has been added to allow the user to specify deck pour locations. The
program uses this information to analyze locations that are in positive bending due to
the deck pour loads (Revision 012.1).
2. Program input has been added for a lateral moment to be applied to the girder during
the constructibility and deck pour analysis. This moment is entered per span and is
applied to all analysis locations in that span (Revision 012.2).
3. Program input has been added to allow the program to internally compute distribution
factors. The program calculates a single value each for moment and shear and single
and multi-lane (four distribution factors total). These values are used over the entire
length of the girder (Revision 012.3).
4. Program input has been added to allow the user to specify use of the design truck only
(without the accompanying lane load). Default behavior will be to include the lane with
the truck (Revision 016).

Summary of March 2013 Revisions - Version 10.1.1.8
1. An error with the processing of the "Reduce web thickness" input item on the web cross
section input has been resolved. Previously, if the checkbox was left unchecked, it would
not be correctly interpreted by the engine. Also, the engine has been revised to never
reduce the web thickness of the section to less than that required by the handling
requirements (D/150 or D/300 for longitudinally stiffened sections) (Revision 004).
1. An input item has been added to the General Properties node to control whether the
input sanity checks are done or not (Revision 003).

Summary of Revisions - Version 10.1.1.7
1. The GUI was converted from Visual Basic .NET to C# .NET.

1. On the "Cross Section" tabs, the column heading "Range" has been changed to "End
Location" (Request B20).
2. The behavior of the "Reduce Web Thickness" input item has been revised to match the
description in the User's Guide (Request B21).
3. Values that are changed in the active cell of a data grid are now saved properly (Request
B22).

1. If the analysis engine is run and the license is expired, the GUI will display a dialog box
and relevant program output in the results window (Request B01).
2. If the analysis engine stops with an error (but otherwise ends without a crash), a dialog
box is displayed and relevant program output to aid the user with revising their input
will be shown in the results window. Also as part of this, if the analysis engine crashes,
multiple engine output files are concatenated and displayed in the results window
(Request B02).
3. The version number of the program has been updated 10.1.1.5 and all references to
"beta" or "draft" have been removed (Request B03).
4. All of the sample input files have been revised to remove the decimal from the end of
the value "99999." for span length and all entries of 0.0 for hinge locations have been
removed. However, 0.0 is now an acceptable value for hinge location (Requests B04 and
B05).
5. The hinge location input field and symmetry combobox (see Request B07) are disabled
for simple span girders (Request B06).
6. A combobox has been added to the "Span Information" form to allow the user to
designate a given span as symmetrical. In combination with this, 99999 is no longer an
acceptable value for span length (Request B07).
7. The program will continue to allow users to open, edit and save input files on a UNC
path, but will no longer run the analysis engine for these files. Users are encouraged to
save such files locally so that they can be run through the analysis engine (Request B08).
8. For NSBA input files, the input item for "Overburden" has been removed from the GUI
"Loads" form, and the output for Overburden has been removed from the program
HTML output file only for NSBA input files by modifying the stylesheet . Note: The
Overburden output was not removed from the program Text output file (.OUT).
(Request B09).
9. For the NSBA version of the program, the upper limits on maximum and minimum
transverse stiffener spacings in the program sanity checks have been increased to three
times the maximum web depth or 432". The limits in the GUI have also been revised to
reflect this (Request B10).
10. The number of decimal places on many of the output values have been reduced, and
many text captions have been changed to uppercase in the HTML output with
modifications to the stylesheet. These changes have been made for both NSBA and
WisDOT versions of the output (Request B11).
11. The generation of the XML output has been modified such that the "Performance ratio
above which messages are output" input value is now followed properly (Request B12).
12. For "Minimum flange thickness" and "Maximum plate thickness" on the "General
Properties" form and "Top Flange Thickness" and "Bottom Flange Thickness" on the
"Cross Section" form, the lower and upper limits have been changed to 0.3125" and 4"
to match internal limits of the analysis engine (Request B13).

13. The word "Required" is now spelled out in the XML output to resolve an issue with
parsing the word when it is abbreviated as "Req'd" (Request B14).
14. The analysis engine will no longer stop with an error if the "Comments, line 1" input
field is left blank (Request B15).
15. The GUI and analysis engine will now properly handle the entry of double quotes (") in
the Model Properties and Comments fields (Request B16). NOTE: Any input files that
have been previously created that have double quotes in the Model Properties or
Comments field still will not work. To fix these files, open them with LRFD Simon and
"Save As...". This will allow the GUI to write out the files with the proper double
double quotes.
16. The display of the GUI splash screen is now hard-coded in "Load" event of frmMain to
avoid very occasional runtime exceptions (Request B17).
17. Upper limits have been removed from the material costs and fabrication cost factors
(Request B18).
18. Pressing "F1" in any input field will open the User's Guide (Request B19).

1. A change has been implemented to avoid the "Invoke or BeginInvoke cannot be called
..." exception that is occasionally seen when starting the program for the first time.
2. The informational screen that appears when choosing "About LRFD Simon" is now
modal; that is, the user cannot change back to the GUI without first closing the About
form.
3. The batch file that actually runs the LRFD Simon engine has been modified to avoid
"Could Not Find" errors when the input model name has spaces in it.

1. Copyright information on the splash screen, About screen and User's Guide has been
updated.

1. The GUI was crashing when creating a new model because it was trying to parse a file
name from "<New Model>". Add a Try/Catch check so if Path.GetFileName returns an
error it just uses what is present in FileNameAndPath.
2. Change the background color of the copyright label on the splash and about screens to
transparent.

1. When the license file is less than 30 days from expiration, the warning message now
states "less than 30" rather than "<30" to avoid issues with parsing the XML output.
2. The caption on the main form of the GUI now includes only the filename rather than
filename and path. Also, only "LRFD Simon" appears.
3. The splash screen no longer displays the version number.

1. Reading and writing of the model files is now handled by the
LRFDSimonInputProcess.dll. Basic documentation of the data structure and methods
exposed by this DLL is included in doc\Use of LRFDSimonInputProcessor.
2. Version number has been revised to v10.1.1.0 and has been synchronized in the GUI,
DLL and engine executable.
3. SIMON_output.XSL has been revised to include a "table of contents" near the top of the
program output.
4. Installer note: SIMON_output.xsl, NSBA.bmp and WisDOT.bmp need to be writeable (i.e.
read-only flag cleared) when installed. These files are copied into the input file
directories so that they are properly displayed and if they are read only, errors will occur
when copying into a directory.

1. First version released for testing.

Simon LRFD

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Simon LRFD

Caricato da

Copyright:

Formati disponibili

LRFD Simon

Certain materials included in this publication are reprinted with the

2 GETTING STARTED ....................................................................................................................................10

3.1 GENERAL .......................................................................................................................................................25

APPENDIX A: QUICK INSTALLATION GUIDE ...................................................................................................... 145

APPENDIX B – REVISION HISTORY.................................................................................................................... 152

LRFD Simon is applicable to non-composite or composite (steel-concrete), doubly symmetric or

 A listing of the input data for user verification;

Tool Strip Buttons

Exhibit 1: Initial Blank Form upon Execution of LRFD Simon.

2.2 Menu Options

Exhibit 2: Help Menu Option: LRFD Simon User's Guide.

Exhibit 3: Help Menu Option: 'About LRFD Simon' Pop-Up Window.

2.2.2.1 New Model

Exhibit 4: File Menu Option: New Model Window.

2.2.2.2 Open Model

Exhibit 5: File Menu Option: Open File.

2.2.2.2.1 Sample Input Files

2.2.2.3 Save Model

2.2.2.4 Save Model As

2.2.2.5 Save Input Verification

2.2.2.6 Model Properties

2.2.2.7 Close Model

2.2.2.8 Print Results

2.2.3 Analyze Menu

2.3 Tool Strip Buttons

Tool Strip Buttons

Input/Output Window Pane

Task Navigation Pane

Exhibit 13: LRFD Simon User Interface Screen.

Exhibit 14: General Properties Form.

If the LRFD Analysis run option is chosen for a

2) The distribution factor used for computing the live-load deflection is

where m is equal to the appropriate multiple presence factor, NL is the

 Cross section must consist of two or more single-cell box sections.

 Distance center-to-center of flanges of adjacent boxes, a, taken at midspan must be no

 Bearing lines must not be skewed.

 The bridge must be straight.

Exhibit 17: Material Properties Form.

The concrete type is used to determine the modulus of

If Yes is chosen, LRFD Simon will consider the slab effective

If Yes is chosen and LRFD Simon determines internally that

If No is chosen, the slab will not be considered effective for

3.5.2 Long-Term Composite Dead Loads

3.5.3 Live Load Information

Exhibit 18: Loads Form.

Note: Both options also include the LRFD fatigue

When Both is chosen, the largest value is applied.

When Both is chosen, the largest value is applied.

Enter the magnitude of the axle load for the user-

Exhibit 22: Transverse Stiffener Properties Form – One-Sided Stiffener Option.

Exhibit 23: Shear Stud Properties Form.

If No is chosen, the remainder of the information on

Exhibit 25: Box Girder Properties Form.

Box girder spacing,

Choose the maximum number of compression

Maximum number Options:

Choose 0 for an unstiffened bottom flange. A

If both the minimum and maximum tee areas

If both the minimum and maximum tee areas

Exhibit 27: Span Information Form.

3.10.2 Symmetrical Span Declaration

3.10.3 Non-Composite Uniform Dead Load