> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow.md).

# Concrete Box Girder Bridge Template

![Concrete Box Girder Bridge workflow overview](https://openbrim.atlassian.net/wiki/download/attachments/2194604379/ConcreteBoxGirderBridgeWorklow.png?api=v2)

The Concrete Box Girder Bridge workflow models a concrete box girder bridge: the multi-cell box running continuously over its supports, its bearings, diaphragms and tendons, the substructure, the staged construction, the loads and combinations, and the code checks.

Work through the groups in order: lay out the alignment and support lines, define the materials and import the box section, place the bearings and the [Concrete Box Girder](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/superstructure-cbg/box-girder-cbg/concrete-box-girder-cbg.md), then add the attachments, substructure, tendons, construction stages, loads, combinations and code checks.

## Workflow groups

The workflow lists these groups, in this order:

1. [Bridge Geometry](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/bridge-geometry-cbg.md): Roadway Alignment, Bridge Alignment, Support Lines, Insertion Point
2. [Properties](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/properties-cbg.md): Materials, Rebars, Strands, Sections, Bolt Properties, Pushover (Hinge Property, Moment-Curvature Report)
3. [Superstructure](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/superstructure-cbg.md): Bearings (Bearing Seat, FEA Bearing, Steel Reinf. Elastomeric Bearing, Pot Bearing, Single Roller Bearing, Sliding Plate Bearing), Box Girder (Concrete Box Girder), Diaphragm (Diaphragm), Temporary Supports (Single Element)
4. [Superstructure Attachments](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/superstructure-attachments-cbg.md): Barrier, Roadway, Rail
5. [Substructure](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/substructure-cbg.md): End Bent, Cantilever Abutment, Integral Abutment, Semi-Integral Abutment, Bent (Bent Cap, Pier Cap, Column), Steel I Girder Bent Cap (Steel I Girder Bent Cap, Diaphragm, Plate), Foundation (Rectangular, Custom, Custom (Abutment only)), Pile (Single Pile, Pile Layout), Soil Structure Interaction (Soil Layer, Soil Set, Backfill Soil), STM (Pier Cap STM)
6. [Tendon](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/tendon-cbg.md): Girder Strand, Girder Tendon, Cap Tendon
7. [Construction](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/construction-cbg.md): Construction Stage, Superstructure Construction, Substructure Construction, Superstructure Deconstruction, Substructure Deconstruction, Changes
8. [Loading](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/loading-cbg.md): Load Geometry Definitions, Loads (Static Loads, Element Loads, Inf. Surf Based LL/BR/CE, Wind Load, Static BR/CE Load, Water Load, Temperature Load, Prestressing Load, Dynamic Loads, Pushover Load, Earth Pressure)
9. [Combinations](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/combinations-cbg.md): Result Extraction (From Stages), Design Load Combinations (Limit States, Load Combination Table)
10. [Templates for Code Check and Load Rating](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/templates-for-code-check-and-load-rating-cbg.md): Concrete Box Girder Code Check Template, Concrete Pier Cap Code Check, Pier Cap STM Code Check Template, Integral Bent Cap Code Check, Concrete Pier Column Code Check, Pier Footing Code Check, Pile Capacity Check, Pile Interaction
11. [Superstructure Code Checks](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/superstructure-code-checks-cbg.md): Concrete Box Girder Code Check
12. [Substructure Code Checks](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/substructure-code-checks-cbg.md): Concrete Pier Cap Code Check, Pier Cap STM Code Check (D-Region), Integral Bent Cap Code Check, Concrete Pier Column Code Check, Pier Footing Code Check, Pile Capacity Check, Pile Interaction
13. [Reports](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/reports-cbg.md): Static Pushover Graph, Elastomeric Bearing Stiffness, Project Inputs, Quantity Takeoff Report, Pay Item Table (Pay Item, WSDOT Pay Item, Kiewit Pay Item)
14. [Geometric Criteria](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/geometric-criteria-cbg.md): Clearance Zone, Vertical Clearance Check
15. [Organization](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/organization-cbg.md): Object Group, Saved Reports, Work Point, Cross-Project Data (Shared Objects, Shared Substructure, Analysis Results)
16. [External References](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/external-references-cbg.md): Project 3D, Project Objects, Project Analysis Results, Imported Data (Digital Terrain Model)
17. [Export](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow/export-cbg.md): DGN Additional Properties, DGN Seed File Configuration, Export

Below the groups, the workflow also lists two generators: Substructure Codecheck and AASHTO IDM. This workflow has no separate Load Rating, CADD or GIS group.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
