> 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-i-girder-bridge-workflow/construction-sig/superstructure-construction-sig/transverse-beam-construction-sig.md).

# Transverse Beam Construction \[SIG]

This object places transverse beams under deck into the construction sequence. From the selected stage onward the beams are part of the structure and their self weight is applied.

![Transverse beams under deck (blue) over steel plate girders, the members this object constructs; deck drawn transparent](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-5d02dde091ff8540011df57457b51048b0b91985%2Ftransverse-beams-under-deck-overview.png?alt=media)

A staged analysis includes a transverse beam only when a construction object constructs it. A beam that no Transverse Beam Construction object constructs is left out of the staged analysis, and it reports no forces. Use one object per stage when the beams are placed in more than one step.

{% hint style="info" %}
**Branching construction sequences**

The beams are active only in stages that follow this stage in the construction sequence. If the sequence branches, for example a deck-pour branch and a separate loading branch, place the object on a stage that comes before every stage whose results should include the beams.
{% endhint %}

## Transverse Beam Construction

**Stage:** The construction stage at which the beams are erected, selected from **Construction Stage**. A value is required.

**Bridge:** The bridge whose transverse beams are considered, selected from **Bridge Alignment**. A value is required.

**Construct All/Selection \[All/Selection]:** Which beams are constructed at this stage.

* **All** constructs every transverse beam on the decks of the selected bridge.
* **Selection** constructs only the beams listed in **Selected Transverse Beams**.

**Selected Transverse Beams:** The beams constructed at this stage, picked from the **Transverse Beams Under Deck** objects in the model. Only editable when **Construct All/Selection** is Selection. At least one beam must be selected.

**Transverse Beam Self Weight Factor:** Scales the self weight of the beams applied at this stage. The default of 1 applies the weight of the beams as modeled.

**Stiffness \[No/Yes]:** With **Yes**, the beams are added to the structure at this stage and carry load. With **No**, the beams do not take part in the structure.

**Filler Load \[Ignore/Include]:** With **Include**, the weight of the girder fillers of the beams constructed here (steel, in the beam material) is applied at this stage, as a point load at each girder crossing. With **Ignore**, the default, it is not applied. The concrete haunch fillets are cast with the deck; their weight is applied by the deck construction object's **Haunch Load**.


---

# 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-i-girder-bridge-workflow/construction-sig/superstructure-construction-sig/transverse-beam-construction-sig.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.