> 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/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/substructure-ex1-stg/foundation-ex1-stg/rectangular-ex1-stg.md).

# Rectangular

This section defines rectangular footing geometry for standard pier columns.

{% hint style="info" %}
**Navigation:** Substructure > Foundation > Rectangular

For detailed parameter explanations, see the [Rectangular Reference](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/substructure-stg/foundation-stg/rectangular-stg).
{% endhint %}

## Steps

### Step 1: Navigate to Rectangular Foundation

Navigate to **Foundation > Rectangular** in the tree view.

![Rectangular foundation navigation](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-093634.png?api=v2)

### Step 2: Assign Substructure

Click the **three-dot icon** on the **Substructure** cell and select **Column1** and **Column2**.

### Step 3: Define Footing Dimensions

Enter the footing dimensions as shown in the table:

| Parameter                 | Description                       |
| ------------------------- | --------------------------------- |
| Footing Width \[ft]       | Width of the rectangular footing  |
| Footing Length \[ft]      | Length of the rectangular footing |
| Longitudinal Offset \[ft] | Offset along alignment            |

![Footing dimensions](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-094042.png?api=v2)

### Step 4: Assign Material

Click the **three-dot icon** on the **Material** cell and select **Fc\_5ksi** concrete material for the rectangular footings.

![Material assignment](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-094116.png?api=v2)

### Step 5: Configure FEM Settings

Navigate to the **FEM** tab and select **RigidSection** for the Rigid Section column.

![FEM settings](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-094459.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Foundation Offsets</summary>

**Longitudinal Offset:** Offsets the foundation along the alignment.

**Transverse Offset:** Offsets the foundation on the y-axis perpendicular to the alignment.

**Rotation:** Rotates the XY plane.

</details>

## Verification

{% hint style="success" %}
The completed rectangular footings are shown below.
{% endhint %}

![Rectangular footings 3D view](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-105019.png?api=v2)

![Rectangular footings plan view](https://openbrim.atlassian.net/wiki/download/attachments/2169110585/image-20230222-105048.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/substructure-ex1-stg/foundation-ex1-stg/rectangular-ex1-stg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
