> 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/openbrimfea/loads-fea.md).

# Loads \[FEA]

The Loads folder holds everything that acts on the structure, organised by how the load is applied.

* [Loads on Nodes & Elements](https://docs.openbrim.org/templates/openbrimfea/loads-fea/loads-on-nodes-elements-fea.md): loads that name the node or element they act on.
* [Loads by Location](https://docs.openbrim.org/templates/openbrimfea/loads-fea/loads-by-location-fea.md): loads placed by coordinate, path or polygon and spread onto the elements of a group that lie there.
* [Imposed Displacements & Strains](https://docs.openbrim.org/templates/openbrimfea/loads-fea/imposed-displacements-strains-fea.md): prescribed movements, temperature and initial strains.
* [Prestressing](https://docs.openbrim.org/templates/openbrimfea/loads-fea/prestressing-fea.md): tendon prestress and cable stressing.
* [Moving Loads](https://docs.openbrim.org/templates/openbrimfea/loads-fea/moving-loads-fea.md): vehicles, design lanes, influence surfaces and lines, and moving load placements.
* [Dynamic Excitation](https://docs.openbrim.org/templates/openbrimfea/loads-fea/dynamic-excitation-fea.md): response spectrum curves, time history functions and support motions.

The cases these loads belong to are under [Analysis](https://docs.openbrim.org/templates/openbrimfea/analysis-fea.md), and the erection sequence under [Staged Construction](https://docs.openbrim.org/templates/openbrimfea/staged-construction-fea.md).

Two things are worth knowing before working anywhere in this folder. Every load belongs to an **analysis case**, and a load with no case assigned applies nowhere, silently. And the **sign** of a load component follows the axis direction - a downward load in a Z-up model is negative.


---

# 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/openbrimfea/loads-fea.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.
