> 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/steel-tub-girder-bridge-workflow/superstructure-stg/stiffeners-stg/bottom-flange-stiffener-stg.md).

# Bottom Flange Stiffeners \[STG]

## General

**Girder**: Specify the girder on which the stiffener will be generated.

**Section**: Assign a section for the stiffener. Sections can either be imported or assigned from previously defined ones under Properties > Sections.

**Start Station**: Specify the start station for the stiffener along the PGL.

**End Station**: Specify the end station for the stiffener along the PGL.

**Trans. Offset from Mid. of Bottom Fla.:** Specify the transverse offset value for the stiffener's location. When looking upstream along the PGL, negative values indicate the left side, while positive values indicate the right side. A value of zero indicates the centerline of the tub girder's bottom flange.

![image-20241024-154457.png](https://openbrim.atlassian.net/wiki/download/attachments/2241232913/image-20241024-154457.png?api=v2)


---

# 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/steel-tub-girder-bridge-workflow/superstructure-stg/stiffeners-stg/bottom-flange-stiffener-stg.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.