> 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/element-loads-cug/girder-load-cug.md).

# Girder Load \[CUG]

## Girder and Stage

**Girder**: Specify the modeled girder to which the defined loads will be applied.

**Stage**: Specify the stage at which the loads will be applied to the girder.

## Girder Line Load

**Applied Flange \[Left/Right/Both]**: The flange at which the defined loads will be applied throughout the girder can be specified using this parameter. This definition will be used for applying the defined load to the nodes.

**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 direction (gravity direction). For typical loads (such as wearing surface loads or stay-in-place formwork loads), 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" %}
**The Directions of Forces** See the figures provided below for further clarification on the directions of positive forces. ![image-20241217-145009.png](https://openbrim.atlassian.net/wiki/download/attachments/2348482741/image-20241217-145009.png?api=v2) ![image-20241217-145115.png](https://openbrim.atlassian.net/wiki/download/attachments/2348482741/image-20241217-145115.png?api=v2) ![image-20241217-145212.png](https://openbrim.atlassian.net/wiki/download/attachments/2348482741/image-20241217-145212.png?api=v2)
{% endhint %}

## Girder Point Load

In the case of applying point loads to a girder object, this section of the girder load can be used.

**Reference Location \[Start/End/Middle]**: The reference location for the point load (start, end, or middle) can be specified using this parameter.

**Offset from Reference Location**: This parameter allows you to offset the point load from the reference location. A positive offset value will move the point load in the upstation direction, while a negative offset will move the point load in the downstation direction.

**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 direction (gravity direction). For typical loads (such as wearing surface loads or stay-in-place formwork loads), 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.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/element-loads-cug/girder-load-cug.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.