> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/substructure-ex1-cug/end-bent-ex1-cug.md).

# End Bent

This section defines the end bent (abutment) structures at both ends of the bridge.

{% hint style="info" %}
**Navigation:** Substructure > Pier > End/Interior Bent

For detailed parameter explanations, see the [End Bent Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/substructure-cug/endinterior-bent-cug).
{% endhint %}

## Steps

### Step 1: Navigate to End Bent

Navigate to **Pier > End/Interior Bent** in the tree view.

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-105204.png?api=v2)

### Step 2: Select Locations

Click the **three-dots icon** on the **Location** cell and select **SL1** and **SL4**.

This determines the placement of the end bents.

### Step 3: Enter Parameter Values

Since **EB1** and **EB2** are identical, enter the same parameter values for both.

![Parameters](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-113830.png?api=v2)

![More Parameters](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-114625.png?api=v2)

![Additional Parameters](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-114707.png?api=v2)

### Step 4: Configure Section Data

Click the **three-dots icon** on **Straight - Tapered Section / Length** and select **Edit**.

Click the **three-dots icon** on the **Start Section** cell and select **EBSec**.

Click the **three-dots icon** on the **End Section** cell and select **EBSec**.

Enter **Section Length** as **45 ft** along Y-Y starting from right.

### Step 5: Set Slope Option

Navigate back to the **General** tab and set **Slope Option** to **Alignment**.

![Slope Option](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-115447.png?api=v2)

Enter the **Top Elevation Offset from Alignment** value as shown.

### Step 6: Configure FEM Settings

Navigate to the **FEM** tab and select a section for **Rigid Section**.

![FEM Settings](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-115653.png?api=v2)

{% hint style="info" %}
OpenBrIM automatically assigns the **RigidSection** defined in Properties to objects like End Bent and Pier Cap.
{% endhint %}

<details>

<summary><strong>Quick Tip:</strong> Transverse Offset Direction</summary>

Offset values use PGL (Profile Grade Line) as the reference point.

![Offset Direction](https://openbrim.atlassian.net/wiki/download/attachments/2104689432/image-20230216-130246.png?api=v2)

</details>

## Verification

{% hint style="success" %}
After completing these steps, the end bents should appear as shown below.
{% endhint %}

![Completed End Bent 1](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-120338.png?api=v2)

![Completed End Bent 2](https://openbrim.atlassian.net/wiki/download/attachments/2258763853/image-20230831-120409.png?api=v2)


---

# 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/substructure-ex1-cug/end-bent-ex1-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.
