> 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/construction-tb/substructure-construction-tb/abutment-construction-tb.md).

# Abutment Construction \[TB]

## Abutment Construction

This object manages the construction staging for abutments in staged construction analysis.

### General

**Stage:** Construction stage in which the abutment is constructed. The finite elements for the abutment are activated and the self-weight is applied at this stage.

**Abutment:** Abutments included in this construction stage.

**Portion \[Full/Below Joint/Above Joint]:** Which part of the abutment is constructed at this stage, so that an abutment cast in two pours can be staged pour by pour.

* **Full** (default): The whole abutment.
* **Below Joint:** The part below the construction joint (the first pour).
* **Above Joint:** The part above the construction joint (the second pour).

Below Joint and Above Joint require every picked abutment to have a construction joint enabled, or, on a Semi-Integral abutment, a generated back wall. A Semi-Integral back wall is cast with the superstructure, so Below Joint constructs the substructure without the back wall and Above Joint constructs the back wall and its connections.

**Self Weight Factor:** Scaling factor applied to the abutment's self-weight during finite-element analysis (default 1.0).


---

# 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/construction-tb/substructure-construction-tb/abutment-construction-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.
