> 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/truss-bridge-workflow/loading-tb/loads-tb/element-loads-tb/point-load-tb.md).

# Point Load \[TB]

The Point Load workflow item applies a concentrated force and moment at a selected insertion point at a chosen construction stage. Use it for loads that act at a single, explicitly located node — utility attachments, equipment, or any miscellaneous concentrated dead load.

## Point Load

**Insertion Point:** Select the insertion point at which the load is applied. The load is assigned to the node associated with that insertion point.

**Stage:** Choose the construction stage at which to apply the point load. When left empty, the load is defined but not activated on any construction stage.

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

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

**Fz (Gravity):** Force in the vertical direction. A positive value indicates a load in the global -Z (gravity) direction, so typical gravity-type loads are entered as positive values.

**Mx:** Moment about the longitudinal axis along the alignment.

**My:** Moment about the axis perpendicular to the alignment.

**Mz:** Moment about the vertical axis.


---

# 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/truss-bridge-workflow/loading-tb/loads-tb/element-loads-tb/point-load-tb.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.