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

# Pier Column

This section defines the pier column geometry, sections, and positions for intermediate supports.

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

For detailed parameter explanations, see the [Pier Column Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/substructure-cug/pier-cug/pier-column-cug).
{% 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/2258632726/image-20230831-133220.png?api=v2)

### Step 2: Assign Cap and Name

Click the **three-dots icon** on the **Cap** cell and select the pier cap. Enter the column name (e.g., **Pier\_1**).

### Step 3: Define Section Data

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

Enter the following parameters:

| Parameter                 | Value  |
| ------------------------- | ------ |
| Section Length (from Top) | 50 ft  |
| Start Section             | ColSec |
| End Section               | ColSec |

![Section Data Edit](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-133400.png?api=v2)

![Section Selection](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-133751.png?api=v2)

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

### Step 4: Set Column Position

Navigate to the **General** tab and enter the position parameters:

| Parameter         | Value  |
| ----------------- | ------ |
| Transverse Offset | ±10 ft |
| Rotation Angle    | 0°     |
| Bottom Elevation  | -35 ft |

![General Tab](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-134236.png?api=v2)

### Step 5: Create All Pier Columns

Repeat the previous steps to create all pier columns:

| Column  | Cap      | Transverse Offset |
| ------- | -------- | ----------------- |
| Pier\_1 | PierCap1 | -10 ft            |
| Pier\_2 | PierCap1 | +10 ft            |
| Pier\_3 | PierCap2 | -10 ft            |
| Pier\_4 | PierCap2 | +10 ft            |

![All Columns](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-140258.png?api=v2)

<details>

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

Offset values use PGL (Profile Grade Line) as the reference point. Positive values offset to the right, negative to the left.

![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 %}

![Completed Columns Plan](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-140706.png?api=v2)

![Completed Columns 3D](https://openbrim.atlassian.net/wiki/download/attachments/2258632726/image-20230831-140729.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/pier-ex1-cug/pier-column-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.
