> 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.md).

# Loading \[CUG]

**Two Types of Load Definitions in OpenBrIM**

1. One method for defining loads is to first model the bridge elements. Then, using the **"Construction"** section, users can apply the self-weight loads of the bridge elements to the structure in a sequence.
2. Alternatively, in the **"Loading"** section of the workflow, users can:

* Define the geometry as a surface (quadrilateral or arbitrary), line, or point.
* Specify the magnitude using the following units:
  * **Surface**: Imperial Units (kips/ft²) or Metric Units (kN/m²)
  * **Line**: Imperial Units (kips/ft) or Metric Units (kN/m)
  * **Point**: Imperial Units (kips) or Metric Units (kN)

In addition to these loads, several other types of loads can be applied, such as **Influence Surface LL/BR/CE Loads, Temperature Loads, Prestress Loads, Wind Loads**, and more.

For a detailed explanation of how to define loads, please refer to the related documentation page.


---

# 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.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.