> 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/pier-ex1-stg/pier-column-ex1-stg.md).

# Pier Column

This section defines the circular pier column geometry and properties.

{% hint style="info" %}
**Navigation:** Substructure > Pier > Pier Column

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

## Steps

### Step 1: Navigate to Pier Column

Navigate to **Pier > Pier Column** in the tree view.

![Pier Column navigation](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-085245.png?api=v2)

### Step 2: Assign Pier Caps

Click the **three-dot icon** on the **Cap** cell and set the pier caps according to the project, then enter the column names.

### Step 3: Define Column1 Section Data

Click the **three-dot icon** on the **Section Data** cell and select **Edit**.

Enter the following parameters for **Column1**:

| Parameter                              | Value      |
| -------------------------------------- | ---------- |
| Section Length (Starts from Top) \[ft] | 35.25      |
| Start Section                          | ColSec\_P2 |
| End Section                            | ColSec\_P2 |

![Column1 section data](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-084923.png?api=v2)

### Step 4: Define Remaining Column Sections

Repeat the previous steps for **Column2** and **Column3**:

**Column2:**

* Section Length \[ft]: **35.25**
* Start Section: **ColSec\_P2**
* End Section: **ColSec\_P2**

**Column3:**

* Section Length \[ft]: **30.58**
* Start Section: **ColSec\_P3**
* End Section: **ColSec\_P3**

![Column sections](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-090147.png?api=v2)

### Step 5: Configure Offsets and Elevation

Enter the **Transverse Offset \[ft]** and **Bottom Elevation \[ft]** data as shown in the figure.

![Offsets and elevation](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-090622.png?api=v2)

### Step 6: Configure FEM Settings

Navigate to the **FEM** tab to review or adjust finite element model settings.

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

<details>

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

Offset values use PGL (Project Geometry Line) as the reference point.

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

</details>

## Verification

{% hint style="success" %}
The completed pier columns are shown below.
{% endhint %}

![Pier columns 3D view](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-091438.png?api=v2)

![Pier columns side view](https://openbrim.atlassian.net/wiki/download/attachments/2169208836/image-20230222-091502.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/pier-ex1-stg/pier-column-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.
