> 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/spliced-i-girder-bridge-workflow/loading-spig/loads-spig/element-loads-spig/barrier-load-spig.md).

# Barrier Load \[SPIG]

## Barrier Load

### Barrier Load

Barrier loads can be defined based on the selected barrier, construction stage, and magnitudes in terms of forces and moments. The load is applied as a line load along the barrier, onto the finite elements of the deck the barrier sits on.

**Barrier:** Select the barrier to which the load will be applied. A barrier must be selected.

**Stage:** Choose the stage at which to apply the load. A stage must be selected.

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

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

**Fz (Gravity):** Force in the vertical direction. A positive value indicates a load in the global -Z or gravity direction. For usual loads (barrier self weight, attached utilities), the user should input positive values.

**Mx:** Moment in the longitudinal direction along the PGL.

**My:** Moment in the direction perpendicular to the PGL.

**Mz:** Moment in the vertical direction.

{% hint style="info" %}
Although **Fz** is applied in the direction of gravity (positive values for **Fz** will correspond to the downward direction, as with gravity), **Mz** will have a positive direction relative to the **+Z** axis or, in other words, in the upward direction.
{% endhint %}

{% hint style="warning" %}
The load is applied along the barrier's line to the finite elements of the barrier's deck, not to the barrier's own elements. A barrier on a deck type that Barrier Load does not support is reported as an issue. A **Stage** must be selected; the load enters the staged analysis only through that stage.
{% 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/spliced-i-girder-bridge-workflow/loading-spig/loads-spig/element-loads-spig/barrier-load-spig.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.
