Modeling Process

The versatility of the program allows users to begin a model using templates, by importing initial geometry from a variety of formats, or "from scratch."  This topic lays out a general process for creating a model using CSiBridge. The intent is to briefly explain the functions of the various commands available in CSiBridge.

  1. Initialize the model. Initializing the model determines the units to be used and the default definitions of all properties, components, loading definitions, design settings, and other defined items. Bridge objects and other physical objects (lines, areas, links, and the like), and assignments to these objects, are not included in the initialization process. Start by clicking the Orb > New command to access the New Model form. The model can be initialized from defaults (Initialize Model from Defaults with Units option) or from a previously defined model (Initialize Model From Previous File option). Use of the previously defined model works well when common defaults are used for multiple models, such as may be the case for a particular project or client.  Set the current units to those to be used most often in the model.

  2. Select a start option. A model can be started from a blank screen, from a template, or by importing the initial geometry  from a variety of formats (Access Database, Excel Spreadsheet, text file, CIS/2, AutoCAD, IFC, IGES,  NASTRAN, STAAD GTSTRUDL,  StruCAD 3D).

Important:  Remember to save your model often!

  1. Create the Layout Line(s). Layout lines are reference lines used for defining the horizontal and vertical alignment of the bridge and the vehicle lanes. Layout lines are defined using stations for distance, bearings for horizontal alignment, and grades for vertical alignment. Layout lines may be straight, bent or curved, both horizontally and vertically. Horizontal curves are circular with spirals, if necessary. Vertical curves are parabolic.

  1. Define lanes on the bridge.  Lanes must be defined before a bridge model can be analyzed for vehicle live loads. Lanes are used in the definition of bridge live type load patterns that are used in static and dynamic multi-step load cases. Lanes can be defined with reference to layout lines or existing frame objects. Typically, when using the bridge modeler, lanes should be defined from layout lines. Lanes can be defined with width, as necessary.

  1. Define properties. CSiBridge supplies default properties when the model is initialized (see 1 above), including material properties, frame section properties, link properties, and rebar sizes. Review or add to those definitions, along with cable and tendon definitions, as follows:  

  1. Define Superstructure components. These component definitions -- deck section, diaphragms, parametric variations -- are defined parametrically as follows:

Note:  If no variations apply, skip this feature.

  1. Define Substructure components. These component definitions -- bearings, restrainers, foundation springs, abutments, bents -- are defined parametrically as follows:

  1. Define vehicle loads. In CSiBridge, vehicles must be defined to analyze a bridge model for vehicle loads. Those vehicle loads are applied to the structure through lanes. In addition, vehicles classes must be defined to analyze a bridge model for vehicle live loads using a moving load load case. Use the following commands to add vehicle load to the bridge model.

  1. Define load patterns. A load pattern is a specified spatial distribution of forces, displacements, temperatures, and other effects that act upon the bridge. Click the Loads > Load Patterns command to access the Define Load Patterns form. A load pattern by itself does not cause any response in the bridge. Load patterns must be applied in load cases in order to produce results. One special type of load pattern available in CSiBridge is the Bridge Live Load pattern. In that type of load pattern, one or move vehicles that move across the bridge can be specified. For each vehicle, the following can be specified:  a time that the vehicle starts loading the bridge, the initial vehicle location, and the direction of travel and the speed of the vehicle. When used in a multi-step static or multi-step dynamic (direct integration time history) load case, this type of load pattern is useful in evaluating special vehicle loads.

  2. Define functions for use in load cases. Response spectrum function definitions are required for creating response spectrum load cases. Time history function definitions are required for creating time history load cases.

  1. Define point, line, area, and temperature loads. Point load definitions define concentrated loads that can be applied to the bridge superstructure; line load definitions define line loads that can be applied to the bridge superstructure; and area load definitions define area loads that can be applied to the bridge superstructure. Each of these types of loads is applied  at specified locations and values using point, line, and area load assignments to the Bridge Object. Temperature gradient in accordance with AASHTO or JTG D60 design codes, or user specification, can be defined. Gradient patterns can be positive and negative. Patterns automatically adjust for superstructure material and geometry. Temperature loads also are assigned  to the Bridge Object.

  1. Define the Bridge Object. The bridge object definition is the main component of the CSiBridge Bridge modeler. Click the Bridge > Bridge Object > New command to display the Bridge Object Data form. Use that form to define the bridge spans and their vertical and horizontal alignments. With the Bridge Object defined, use the other commands on the Bridge tab to assemble the various components comprising the bridge (e.g., abutments, bents, tendons and so on). This process assigns the definitions created in the previous steps to the Bridge Object.

Anytime the bridge object definition is modified, the linked model must be updated for the changes to appear in the CSiBridge object-based model.

  1. Update the model/create the object-based model. Updating a linked model creates the CSiBridge object-based model from the bridge object definition. The Bridge > Update > Auto Update command is a toggle that by default is enabled (i.e., the model updates automatically). If an object based model of the bridge object exists before the update, that model is deleted when the new object-based model is created. The new object based model includes all of the latest changes to the bridge object definition. Clicking the Bridge > Update > Update command displays the Update Bridge Structural Model form. The options on that form can be used to specify creation of spine models, area object models, and solid object models when the model is updated. The type of object based model created from the bridge object definition can be switched at any time. The update linked model command allows specification of the discretization of the object based model. In some cases, assignment of user-defined discretization points to the bridge object may be warranted to control the discretization of the object based model.

  2. Define load cases for analysis. A load case defines how loads are to be applied to the structure (e.g., statically or dynamically), how the structure responds (e.g., linearly or nonlinearly), and how the analysis is to be performed (e.g., modally or by direct-integration). Click the Analysis > Type > {Type, e.g., Static, Nonlinear Staged Construction and so on} > New command to display the Load Case Date {Type} form.  Any load case type can be used when analyzing a bridge model. For seismic analysis, static, response spectrum and time history load case types are useful. Pushover analysis can be performed using a nonlinear static load case. Staged construction analysis is also performed using nonlinear static load cases. There are several analysis options that are specialized for analysis of vehicle live loads. Moving load load cases compute influence lines for various quantities and solve all permutations of lane loading to obtain the maximum and minimum response quantities. Multi-step static and multi-step dynamic (direct integration time history) load cases can be used to analyze one or more vehicles moving across the bridge at a specified speed. These multi-step load cases are defined using special bridge live load patterns that define the direction, starting time and speed of vehicles moving along lanes.

  1. Specify the moving load case results to be saved.  Analysis of moving load cases involves calculations that are computationally intensive and can take a significant amount of time for larger models. Click the Analysis > Bridge > Bridge Response command to display the Moving Load Case Results Saved form and explicitly specify the analysis results required for a moving-load analysis. Only the results specified will be calculated and saved by the program. If correspondence is to be considered,  for each maximum or minimum response computed, the corresponding force, moment or stress quantities that occur at the same time as the maximum or minimum value also are reported.  For example, in a frame object, when the maximum M3 moment is calculated, if correspondence is specified, the P, V2, V3, T and M2 values that occur at the same time as the maximum M3 value will be reported.  Including correspondence increases the program calculation time and the quantity of response output.

  2. Specify the analysis options to be used during analysis. Click the Analysis > Analyze > Analysis Options command to display the Analysis Options form. Use the form to select the global degrees of freedom that are allowed to be active at every joint in the structure. Use this feature carefully! For most models with three-dimensional behavior, all six degrees of freedom should be available. The form also can be used to specify that an Access database file or an Excel tabular file be written automatically every time an analysis is run. The input parameters and output results to be saved, as well as the filename, can be specified. The feature is particularly useful when running multiple models in batch mode. However, when analyzing different cases in separate runs within the same model, be careful not to overwrite the database file with each fun.

    If your model has objects that require manual meshing, use the manual meshing options available using the Advanced > Edit > Lines > Divide Frames, Advanced > Edit > Areas > Divide Areas, or Advanced > Edit > More > Divide Solids commands to mesh those objects.

  3. Run the analysis. Click the Analysis > Analyze > Run Analysis command to display the Set Load Cases to Run form. Use the form to check the analysis status of the cases, delete result for cases that have already been run, set which cases are to be run, and to run the analysis or save the settings. After an analysis has been run, the Analysis > Analyze > Last Run command can be used to display a form that shows the results of the last analysis that was run.

    When the analysis is complete, a deformed shape of the model will automatically display. If desired, animate the deformed shape and mode shape in 3D perspective by clicking the Start Animation button in the status bar at the bottom of the screen. Animate shell structures displaying stress contours with the corresponding deformed shapes in full in 3D perspective. While displaying mode shapes, the mode being displayed can be instantaneously changed with the '+/-' buttons that will appear at the bottom of the screen.

  4. Adjust the model geometry. Click the Analysis > Shape Finding > Modify Geometry command to display the Modify Undeformed Geometry form. Use the options on the form to modify the undeformed geometry of the structure to achieve a desired deformed shape. The original undeformed geometry of the structure (geometry when the structure was first defined) is assumed to be the target for the deformed geometry of the structure under a user-specified load case. The Analysis > Shape Finding > Reset Geometry command can be used to restore the original geometry.

  5. Specify the load combinations to be used in design. Program design is based on a set of loading combinations. In CSiBridge, load combinations, or combos, are generated automatically by the program or user defined. Click the Design/Rating > Load Combinations > Add Defaults command to display the Add Code-Generated User Load Combinations form and add the program generated automatic load combos. Click the Design/Rating > Load Combinations > New command to display the Load Combinations Data form and define user combinations. (Note that the Advanced > Frame Design > {Steel or Concrete} > Select Design Combos command can be used to work with automatic load combinations.)

  6. Complete superstructure design. Click the Design/Rating > Superstructure Design > Preferences command to display the Bridge Design Preferences form and verify / specify the design code. Then click the Design/Rating > Superstructure Design > Design Requests command to display the Bridge Design Requests - {Code} form; use that form to access the Bridge Design Request - Superstructure - {Code} form. The design request definition requires a unique design request name, selection of the bridge object for which the design request is being defined;  the check type (flexure, stress shear, and so on), station range (portion of the bridge to be designed), design parameters (e.g., stress factors), and demand sets (i.e., loading combinations; see previous step). Some check types include consideration of LLDFs. Users can chose how these factors are determined:  user specified; in accordance with the code; directly from individual girder forces from CSiBridge; or uniformly distributed onto all girders. Note that the only time multiple lanes are necessary for a design is when the ”r;directly from individual girder forces from CSiBridge” method is selected. Otherwise, moving live loads should be applied to only a single lane. The extent to which a vehicle load may be applied to a bridge deck is defined in the bridge deck definition (see Select Bridge Deck Section Type Form). After the Design Request is complete, click the Design/Rating > Superstructure Design > Run Super command to display the Perform Bridge Design - Superstructure form; choose the design request to be designed. The Bridge Object Response Display form will display when design is complete; use the form to evaluate design results.

    If the bridge model if for a steel girder bridge, the Design/Rating > Superstructure Design > Options command will be available. Clicking that command will display the Bridge Object Superstructure Design and Optimization form. Use the options on the form to interactively optimize design of the bridge model.

  7. Complete Seismic Design. Click the Design/Rating > Seismic Design > Preference command to display the Bridge Design Preferences form and verify / specify the design code. Then click the Design/Rating > Substructure Design > Design Requests command to display Bridge Seismic Design Requets - {Code} form; use that form to display the Bridge Design Requests - Substructure Seismic - {Code} form; use that form to select the Bridge Object to be designed and the overwrites to be applied during design.  After the Design Request is complete, click the Design/Rating > Seismic Design > Run Seismic command to display the Perform Bridge Design - Seismic form; choose the design request to be designed. The Bridge Seismic Design form will display when design is complete; use the form to evaluate design results. A seismic design report can be generated by clicking the Design/Rating > Seismic Design > Report command.

  8. Complete a Load Rating. Click the Design/Rating > Load Rating > Preference command to display the Bridge Design Preferences form and verify / specify the design code. Then click the Design/Rating >Load Rating > Rating Requests command to display the Bridge Rating Requests form; use that form to display the Bridge Rating Request - {Code} form. Use that form to specify the loading to be analyzed. Then click the Design/Rating > Load Rating > Run Rating command to display the Perform Bridge Superstructure Rating form. Use that form to set the action for individual rating requests or for all rating requests simultaneously.

  1. Review Results. Use the Home > Display > Show Tables command to review the model input. Alternatively, right click on an object to display assignment and load data on an object-by-object basis. Use the other display features available on Home > Display to display analysis results on your model or on the screen in a tabular format. See the topics in the Home tab > Display panel folder of this Help for more information about displaying results (Show Bridge Forces/Stresses, Show Shell Force/Stress Plots, Show Lanes, Show Bridge Superstructure Design Results, Show Joint Reaction Forces, Show Influence Lines/Surfaces and so on).

Use the Home > View > Set Display Options command to toggle on the display of various input items. Examples of the items that can be toggled on and off include labels, section properties, releases, springs, local axes, and the like.

  1. Print Results. If desired, use the Orb > Print > Print Tables  command to print input and output data to a file or to the printer in tabular form compatible with Word, standard text editors, and .html editors. Or use the Orb > Report > Report Setup command and the Orb > Report > Create Report command to generate output in a variety of report formats, including user specified contents, for selected groups of objects, using a selected orientation, with a cover page and hyperlinked contents, using selected load patterns, load cases/combos, output options, and selected results, and compatible with Word, standard text editors, and .html editors.

Alternatively, use the Orb > Export > Access command to save the input data in a database file that can be reviewed, modified and printed using Microsoft Access or the Orb > Export > Excel command to save the input data in a spreadsheet file that can be reviewed, modified and printed using Microsoft Excel.