> 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/abutment-surface-load-tb.md).

# Abutment Surface Load \[TB]

## Abutment Surface Load

Applies a pressure to the top of an abutment at a selected construction stage. The pressure acts over the top footprint of the abutment (the wall plus both wing wall tops) and is distributed to the top row of nodes of the abutment's finite element mesh, not to the whole wall. Because the inputs are pressures, the total force is the pressure times the footprint area and does not change when the mesh is refined. It supports the Cantilever, Integral and Semi-Integral abutments.

### Abutment Load

**Abutment:** Pick the abutment to load. Only abutments that support top loads can be used (Cantilever, Integral and Semi-Integral); any other pick is reported as a validation issue, because no load would be applied. The user must provide a value.

**Portion \[Abutment Top/First Pour Top (Construction Joint)]:** Which top surface the pressure acts on.

* **Abutment Top** (default): The final top of the abutment.
* **First Pour Top (Construction Joint):** The top of the first pour, at the construction joint, for an abutment built in two lifts. Use it for a load applied in a stage after the first lift and before the second, when the final top has not been cast yet. The loaded area is then the first pour top: the wall plus only the wing walls the joint crosses. On an abutment without a construction joint the load falls back to the abutment top.

**Stage:** The construction stage at which the load is applied. The user must provide a value.

**Fx:** Pressure in the longitudinal direction of the alignment.

**Fy:** Pressure in the transverse direction of the alignment.

**Fz (Gravity):** Vertical pressure. A positive value acts downward, in the direction of gravity; a negative value acts upward.

**Mx:** Distributed moment about the longitudinal axis of the alignment, per unit area.

**My:** Distributed moment about the transverse axis of the alignment, per unit area.

**Mz:** Distributed moment about the vertical axis, per unit area.

**Total Vertical Force (readonly):** The total vertical force the load applies: Fz times the area of the loaded top surface, reported in the global Z sign convention, so a downward load reads negative. Use it to check that the abutment, the Portion and the pressure together give the intended load. It reads zero when the picked abutment does not support top loads. It may take a moment to update after a change. (Read-only)


---

# 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/abutment-surface-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.
