> 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/templates/spliced-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-spig/pile-interaction-t-spig.md).

# Pile Interaction \[SPIG]

Template that drives the Pile Interaction code check. Holds the load combination table and resistance factors used to compute pile axial-moment interaction.

## General

**Load Combination Table:** Load combination table used to combine analysis result cases into AASHTO limit states. All factored forces used by the pile interaction check come from this table.

## Design Parameters

**Ignore Rebar Tendon in Section Property Calc \[Yes/No]:** When Yes, longitudinal reinforcing bars and tendons are ignored when computing the pile section's gross-area properties (inertia, section modulus). When No, they are included in the gross-section property calculation.

**\[NAME\_ALIAS:Φ\_f]Resistance Factor Compression Controlled Section:** Resistance factor applied to compression interactions (default per AASHTO LRFD 5.5.4.2).

**\[NAME\_ALIAS:Φ\_f]Resistance Factor Tension Controlled Section:** Resistance factor applied to tension interactions.


---

# 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/templates/spliced-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-spig/pile-interaction-t-spig.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.