> 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/loading-tb/loads-tb/element-loads-tb/floor-beam-line-load-tb.md).

# Floor Beam Line Load \[TB]

## Floor Beam Line Load

Applies a uniformly distributed force and moment over a portion of a floor beam at a selected construction stage. The loaded portion is located from the right end of the floor beam. On a floor beam modeled with web shells, the load is applied to the top flange line.

### Floor Beam Line Load

**Floor Beam:** Pick the floor beam to load. The user must provide a value.

**Stage:** The construction stage at which the load is applied. The user must provide a value.

**Location Input Method \[Distance from Right End/Relative Position]:** How the start and end of the loaded portion are entered.

* **Distance from Right End:** The start and end are entered as distances measured in plan along the floor beam from its right end.
* **Relative Position** (default): The start and end are entered as fractions of the floor beam length, from 0 at the right end to 1 at the left end. The default covers the full length of the floor beam.

The right end is the end on the right when looking upstation along the alignment.

**Start Relative Position from Right End (0-1):** The start of the loaded portion as a fraction of the floor beam length. Available when Location Input Method is Relative Position.

**End Relative Position from Right End (0-1):** The end of the loaded portion as a fraction of the floor beam length. Available when Location Input Method is Relative Position.

**Start Distance from Right End:** The start of the loaded portion as a distance from the right end of the floor beam. Available when Location Input Method is Distance from Right End.

**End Distance from Right End:** The end of the loaded portion as a distance from the right end of the floor beam. Available when Location Input Method is Distance from Right End.

**Resolved Start Distance from Right End (readonly):** The distance from the right end at which the loaded portion actually starts. A start or end outside the floor beam is moved to the nearest end and reported as a validation issue. (Read-only)

**Resolved End Distance from Right End (readonly):** The distance from the right end at which the loaded portion actually ends. A start and end at the same point is reported as a validation issue. (Read-only)

**Fx (Along Bridge):** Distributed force along the bridge, in the longitudinal direction of the alignment, per unit length of the loaded portion.

**Fy (Transverse):** Distributed force in the transverse direction of the alignment, per unit length.

**Fz (Gravity):** Distributed vertical force per unit length. A positive value acts downward, in the direction of gravity; a negative value acts upward.

**Mx:** Distributed moment about the longitudinal axis of the alignment, per unit length.

**My:** Distributed moment about the transverse axis of the alignment, per unit length.

**Mz:** Distributed moment about the vertical axis, per unit length.

{% hint style="info" %}
Although a positive **Fz** acts downward, in the direction of gravity, a positive **Mz** follows the right-hand rule about the upward **+Z** axis.
{% endhint %}


---

# 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/loading-tb/loads-tb/element-loads-tb/floor-beam-line-load-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.
