> 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/substructure-cug/abutment-system-cug.md).

# Abutment System \[CUG]

## Abutment System

Several types of abutments can be modeled on OpenBrIM. Each one is placed on the support line selected in its **Location** input.

In most bridge workflows the **Abutment System** group holds these items:

* **Abutment types:** Cantilever Abutment, Integral Abutment, Semi-Integral Abutment, PennDOT Integral Abutment, and End/Interior Bent (a bent cap that piles or pier columns support).
* **Approach and joint items:** Approach Slab, Sleeper Slab, Sleeper Slab Head Wall, Strip Seal and Drainage.

Items marked *(deprecated)* in the tree are kept only so that older projects still open; use the items above for new work. The footing under an abutment is modeled with the footing items under **Substructure > Foundation**.

For further clarification on each type and detailed explanations of the associated parameters, please refer to the relevant 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 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/concrete-u-girder-bridge-workflow/substructure-cug/abutment-system-cug.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.
