# Concrete Pier Column Code Check \[CUG]

## Concrete Pier Column Code Check \[CUG]

### General

**Code Check Template:** The code check template is utilized to extract global parameters, results from finite element analysis, and limit states employed in the design process.

**Pier :** Pier for code check. The selected object is only used for extracting the results of an analysis and performing demand computation. Capacity computation will rely on the reinforcement information and section collected in this section.

**Code Check Loc and Rebar Data:** Select a section that contains longitudinal rebars. This section will be used for capacity computations at the proposed station entered in the 'Force Station(from Top of the Column)' parameter.

* **Force Station(from Top of the Column):** The code check station is measured from the top of the column.
* **Stirrup Rebar Profile:** Choose the rebar profile.
* **Spacing of Stirrups:** The distance between each stirrup at the specified force station.
* **Num. of legs in Dir Z:** The number of legs in the Z direction of the column section.
* **Num. of legs in Dir Y:** The number of legs in the Y direction of the column section.
* **Stirrup Rebar material:** Choose the material.

**Shear Reinforcement Type \[Spiral/Tie]:** Spiral reinforcement is a continuous helical reinforcement used to resist lateral forces and provide confinement to the concrete core, while tie reinforcement connects two or more structural elements together to resist tensile forces and create a continuous load path for the structure.

![](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20230319-202646.png?api=v2)

**Detailed Report PDF Name (Export):** This parameter allows the name of the code check document to be modified when saving it as a PDF. When renaming the file, special attention must be given to the text characters on the [linked](https://docs.openbrim.org/faq/general/faq-illegal-chars) page, as certain characters may interfere with parametric equations and lead to unexpected results.

**State Provisions PDF Name (Export):** When **'State Provisions'** is selected, this parameter allows customization of the generated code check report’s name. As with the **'Detailed Report PDF Name'** input parameter, careful attention must be paid to the use of illegal characters.

## Design Parameters

**Effective Length Factor (K\_eff) Z dir.\[2.1/2/1.2/1/0.8/0.65]:** Effective length factor for compression members per AASHTO 4.6.2.5, applied in the Z direction of the column section.\
**Effective Length Factor (K\_eff) Y dir.\[2.1/2/1.2/1/0.8/0.65]:** Effective length factor for compression members per AASHTO 4.6.2.5, applied in the Y direction of the column section.

![image-20240224-235730.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240224-235730.png?api=v2)

![image-20240224-235820.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240224-235820.png?api=v2)

![image-20240224-235826.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240224-235826.png?api=v2)

**Param. of the Effect of Moment-Curvature (Cm) Z dir \[EQN 4.5.3.2.2b-6]:** Moment magnification factor used in the Z direction of the column section (AASHTO Eqn 4.5.3.2.2b-6).\
**Param. of the Effect of Moment-Curvature (Cm) Y dir \[EQN 4.5.3.2.2b-6]:** Moment magnification factor used in the Y direction of the column section (AASHTO Eqn 4.5.3.2.2b-6).

![image-20240225-001032.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240225-001032.png?api=v2)

{% hint style="warning" %}
As seen in the drawings below,

* The axis of the column is the **X direction**
* The longitudinal direction of the alignment is the **Z direction** of the column section
* The transverse direction of the alignment is the **Y direction** of the column section.

Be aware that the rotation angle of the column does not change the local column directions, and the rotation angle is applied to the column clockwise.
{% endhint %}

![image-20240729-192832.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240729-192832.png?api=v2)

![image-20240729-192905.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240729-192905.png?api=v2)

![image-20240729-193526.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240729-193526.png?api=v2)

![image-20240729-193732.png](https://openbrim.atlassian.net/wiki/download/attachments/2126086290/image-20240729-193732.png?api=v2)


---

# Agent Instructions: 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:

```
GET https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/substructure-code-check-cug/concrete-pier-column-code-check-cug.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.