> 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-segmental-bridge-workflow.md).

# Concrete Segmental Bridge Template

The Concrete Segmental Bridge Template models a post-tensioned concrete segmental box girder bridge: the individual precast or cast-in-place segments, the cantilever and draped tendons that stitch them together, and the staged construction sequence that erects them segment by segment.

Work through the items in order — lay out the girder and its segments, define the tendons, then build the erection sequence and the loads and code checks that go with it.

Each Segmental Girder is one segment, placed along a Girder Layout between a start and an end station. For a box modeled as one girder running between two support lines, use the [Concrete Box Girder Bridge workflow](https://docs.openbrim.org/templates/concrete-box-girder-bridge-workflow.md) instead.

## Workflow groups

The workflow lists these groups, in this order:

1. [Bridge Geometry](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/bridge-geometry-cbs.md): Roadway Alignment, Bridge Alignment, Support Lines, Insertion Point, Girder Layout
2. [Properties](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/properties-cbs.md): Materials, Rebars, Strands, Sections
3. [Superstructure](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/superstructure-cbs.md): Bearings (Bearing Seat, FEA Bearing, Steel Reinf. Elastomeric Bearing, Pot Bearing, Single Roller Bearing, Sliding Plate Bearing), Custom Girder (Segmental Girder), Temporary Supports (Single Element)
4. [Superstructure Attachments](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/superstructure-attachments-cbs.md): Barrier, Roadway, Rail
5. [Substructure](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/substructure-cbs.md): Abutment System (Cantilever Abutment, Integral Abutment, Semi-Integral Abutment, State Abutments, Backfill Soil, Approach Slab, Sleeper Slab, Sleeper Slab Head Wall, Strip Seal, Drainage), End Bent, Pier (Pier Cap, Pier Column, Cheek Wall), Foundation (Rectangular, Custom, Custom (Abutment only)), Pile (Single Pile, Pile Layout), Earthwork (Structure Backfill, Structure Excavation), STM (Pier Cap STM)
6. [Tendon](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/tendon-cbs.md): Girder Strand, Cantilever Tendon, Draped Tendon, Cap/Bent Tendon, Column Tendon
7. [Construction](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/construction-cbs.md): Construction Stage, Superstructure Construction (Bearing, Segment Construction, Segment Construction (Complete), Barrier Construction, Temporary Support), Substructure Construction, Superstructure Deconstruction, Substructure Deconstruction, Changes
8. [Loading](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/loading-cbs.md): Load Geometry Definitions, Loads (Static Loads, Element Loads, Inf. Surf Based LL/BR/CE, Wind Load, Temperature Load, Prestressing Load)
9. [Combinations](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/combinations-cbs.md): Result Extraction Cases, Design Load Combinations (Limit States, Load Combination Table)
10. [Templates for Code Check](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/templates-for-code-check-cbs.md): Concrete Girder Code Check Template, Concrete Pier Cap Code Check, Pier Cap STM Code Check Template, Concrete Pier Column Code Check, Pier Footing Code Check, Pile Capacity Check, Pile Interaction
11. [Superstructure Code Checks](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/superstructure-code-checks-cbs.md): Concrete Segmental Girder Code Check
12. [Substructure Code Checks](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/substructure-code-checks-cbs.md): Concrete Pier Cap Code Check, Pier Cap STM Code Check (D-Region), Concrete Pier Column Code Check, Pier Footing Code Check, Pile Capacity Check, Pile Interaction
13. Reports: Center of Gravity
14. [Access Hole Design](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/access-hole-design-cbs.md): Access Hole Model, Access Hole Load
15. [CADD](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/cadd-cbs.md): Plan and Elevation CADD, Foundation Plan CADD, Abutment Plan CADD
16. Geometric Criteria: Clearance Zone, Vertical Clearance Check
17. External References: Imported Data (Digital Terrain Model)
18. [Export](https://docs.openbrim.org/templates/concrete-segmental-bridge-workflow/export-cbs.md): DGN Additional Properties, Export


---

# 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-segmental-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.
