> 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/truss-bridge-workflow/superstructure-tb/cross-frames-and-floor-beams-tb/support-beam-tb.md).

# Support Beam \[TB]

For floor beams, support beams can be modeled using the parameters listed below.

## Support Beam

**Floor Beams:** Previously modeled floor beams can be used to define the location of the support beams in the longitudinal direction.

**Section:** A section previously defined under **Properties > Sections** or a new section can be imported and assigned to the support beams. The data associated with this parameter will directly affect the Finite Element Analysis (FEA), Finite Element Model (FEM), and the 3D model.

**Transverse Offset (from PGL):** This parameter can be used to define the location of the support beam in the transverse direction.


---

# 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/truss-bridge-workflow/superstructure-tb/cross-frames-and-floor-beams-tb/support-beam-tb.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.