> 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/deck-load-tb.md).

# Deck Load \[TB]

Surface loads to be applied to the deck can be specified by defining the parameters listed below.

## Deck Load

**Stage:** Choose the stage at which to apply the load.

**Deck:** Specify the deck on which to apply the loads.

**Fx:** Force in the longitudinal direction along the PGL.

**Fy:** Force in the direction perpendicular to the PGL.

**Fz (Gravity):** A positive value indicates a load in the global -Z direction (or gravity direction). For typical loads, such as wearing surface loads (with the understanding that this load will be applied to the deck as a whole, while the wearing surface may only cover part of the deck, such as the area between the barriers and in this case, the ***Static Loads - Surface Load*** can be used ), the user should input positive values.

{% hint style="info" %}
**The Directions of Forces** See the figures provided below for further clarification on the directions of positive forces. ![image-20241215-112416.png](https://openbrim.atlassian.net/wiki/download/attachments/2830762281/image-20241215-112416.png?api=v2) ![image-20241215-112601.png](https://openbrim.atlassian.net/wiki/download/attachments/2830762281/image-20241215-112601.png?api=v2) ![image-20241215-112737.png](https://openbrim.atlassian.net/wiki/download/attachments/2830762281/image-20241215-112737.png?api=v2)
{% 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/deck-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.