> 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/truss-bridge-workflow/templates-for-code-check-and-load-rating-tb/pier-cap-stm-code-check-template-t-tb.md).

# Pier Cap STM Code Check Template \[TB]

## Pier Cap STM Code Check Template

The Pier Cap STM Code Check Template holds the project-wide settings of the strut-and-tie check of pier caps per AASHTO LRFD 9th Edition, 5.8.2. Each Pier Cap STM Code Check (D-Region) object points at one template, so these values do not have to be repeated for every pier cap. The check applies AASHTO 5.8.2 only; there is no state provision option.

The Pier Cap STM truss does not reference this template: its own Load Combination Table input sets the combination its bearing reactions and cap weight factor are read under.

### General

**Load Combination Table:** The load combination table that maps the analysis result cases and their factors to the limit states used by the check. The user must provide a value.

### Design Parameters

**Resistance Factor, Compression in STM:** The resistance factor φ applied to the compressive resistance of struts and node faces in a strut-and-tie model, per AASHTO LRFD 5.5.4.2 as required by 5.8.2.3. The default is 0.70. It must be greater than 0 and not more than 1.

**Resistance Factor, Tension in STM:** The resistance factor φ applied to the tensile resistance of the ties in a strut-and-tie model, per AASHTO LRFD 5.5.4.2 as required by 5.8.2.3. The default is 0.90. It must be greater than 0 and not more than 1.


---

# 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/truss-bridge-workflow/templates-for-code-check-and-load-rating-tb/pier-cap-stm-code-check-template-t-tb.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.
