> 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.md).

# Stiffeners \[STG]

Stiffeners in OpenBrIM do not have a finite element model (FEM); however, they can be modeled to enhance the 3D representation and used for design and code checks. However, the weight loads of these elements can be applied to the structure if the related definitions are made.

If the weight loads of these elements need to be applied to the bridge model, several parameters are available in the spreadsheet under **Construction → Superstructure Construction → Girder Erection (Partial) / Girder/Cross-Frame Erection (Complete)**. By setting the relevant parameters to **'Include'** or **'Ignore,'** the weight loads of the modeled connection elements can either be applied or excluded.

The parameters available for such definitions are:

* In both spreadsheets, **Girder/Cross-Frame Erection (Complete)** and **Girder Erection (Partial)**:
  * **Splice Load \[Include/Ignore]**
  * **Stiffener/Gusset Plate Load \[Include/Ignore]**

Three types of stiffeners can be modeled for Steel Tub Girder Bridges:

For a detailed description of these objects, please refer to the object documentation.


---

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