> 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/loading-sig/loads-sig/element-loads-sig/pier-cap-line-load-sig.md).

# Pier Cap Line Load \[SIG]

Line loads for pier caps can be applied based on the definitions made using the parameters below.

## Pier Cap Load

**Pier Cap:** Choose the pier cap to impose the line load.

**Stage:** Select a stage to apply the load.

**Start Normalized Distance From Right (0-1)**: The relative distance where the line load starts must be specified with a value between 0 and 1, where 0 corresponds to the initial node of the selected pier cap, and 1 corresponds to the final node. The initial node is defined along the alignment direction, looking upstation (to the right in the standard view).

**End Normalized Distance From Right (0-1)**: The relative distance where the line load ends must be specified with a value between 0 and 1, where 0 corresponds to the initial node of the selected pier cap, and 1 corresponds to the final node. The initial node is defined along the alignment direction, looking upstation (to the right in the standard view).

**Fx**: Force in the X direction with respect to the global coordinate system.

**Fy**: Force in the Y direction with respect to the global coordinate system.

**Fz** (**Gravity**): Force in the Z direction with respect to the global coordinate system.

**Mx**: Moment in the global X-axis direction.

**My**: Moment in the global Y-axis direction.

**Mz**: Moment in the global Z 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.

**The Directions of Forces** See the figures provided below for further clarification on the directions of positive forces and moments. ![image-20250121-111920.png](https://openbrim.atlassian.net/wiki/download/attachments/2409103861/image-20250121-111920.png?api=v2) ![image-20250121-112057.png](https://openbrim.atlassian.net/wiki/download/attachments/2409103861/image-20250121-112057.png?api=v2) ![image-20250121-112220.png](https://openbrim.atlassian.net/wiki/download/attachments/2409103861/image-20250121-112220.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/steel-i-girder-bridge-workflow/loading-sig/loads-sig/element-loads-sig/pier-cap-line-load-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.