> 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-code-checks-ex1-stg/pier-footing-code-check-ex1-stg.md).

# Pier Footing Code Check

{% hint style="info" %}
**Navigation:** Substructure Code Checks > Pier Footing Code Check

For detailed parameter explanations, see the [Pier Footing Code Check Reference](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/substructure-code-checks-stg/pier-footing-code-check-stg.md).
{% endhint %}

**Step 1:** In this section, please specify Pier Footing the code check will be applied to.

**Step 2:** Navigate to Substructure Code Checks > **Pier Footing Code Check**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-092250.png?api=v2)

**Step 3:** Click **three-dots icon** on **Select Pier Footing** and select as **RF1**

(As a different way, the relevant Pier Footing can be selected on the 3D view by clicking "Pick".

**Step 4:** Click **three-dots icon** on **Pier Footing Template**.

Select the **PFCCT1** "Pier Footing Code Check" template defined in the previous steps for all.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-092516.png?api=v2)

**Step 5:** Enter code check station in longitudinal and transverse directions by **Distance in Longitudinal direction from centroid \[ft]** and **Distance in Longitudinal direction from centroid \[ft]** as **3**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-104411.png?api=v2)

**Step 6:** Quick Tip

How determine "Distance in Longitudinal & Transverse direction from centroid \[ft] parameters?

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-105139.png?api=v2)

The point indicated by the red circle is the point where the code is checked for pier footing.

Enter 3 for **"Distance in Longitudinal direction from centroid \[ft]"** and **"Distance in Longitudinal direction from centroid \[ft]"** parameters.

This is because the section edge of the column **(Col\_Sec2)** has **6 ft** (72 in), half of this value is entered.

**Step 7:** Navigate **Flexural Reinforcements** tab.

Set **Reinforcement Material** as **A615\_60.**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-110731.png?api=v2)

**Step 8:** Click **three-dots icon** on **Longitudinal Direction Reinforcements** and click Edit.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-111010.png?api=v2)

**Step 9:** There are 2 types of Flexural Reinforcement in the section, **Bottom** and **Top**.

**Step 10:** Enter Parameters in combobox as follows for both:

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-112909.png?api=v2)

**Step 11:** Rebar Profile as **ASTMA615No6**

Spacing of Reinforcements \[in] as **10**

Distance to Extreme Fiber (concrete cover) \[in] as **4**

**Step 12:** Repeat previous step (row 11) for **Transverse Direction Reinforcements**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-114457.png?api=v2)

**Step 13:** Navigate **Shear Reinforcements** tab.

Set Reinforcement Profile as **ASTMA615No6** for Longitudinal and Transverse direction

![](https://openbrim.atlassian.net/wiki/download/attachments/2169929764/image-20230228-115002.png?api=v2)

***

{% hint style="success" %}
The Pier Footing Code Check have been created.
{% endhint %}

***

If icon won't appear, collapse page tree menu by clicking on arrow or using shortcut "\[".

\| `PFCC1 PFCCT1 RF1 3 3 All` | `PFCC1 A615_60 [[1, ASTMA615No6, 10, 4],[0, ASTMA615No6, 10, 4]] [[1, ASTMA615No6, 10, 4],[0, ASTMA615No6, 10, 4]]` | \`\`\` PFCC1 ASTMA615No6 ASTMA615No6 6 6 2 2 Include

```|
```


---

# 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/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/substructure-code-checks-ex1-stg/pier-footing-code-check-ex1-stg.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.