> 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/construction-tb/substructure-construction-tb/pier-stem-construction-tb.md).

# Pier Stem Construction \[TB]

This object manages the construction staging for pier stems in staged construction analysis of the truss bridge.

## Stem Construction

**Stage:** Select the construction stage in which the pier stems will be constructed. The finite elements for the stems are activated and their self-weight is applied during this stage.

**Stems:** Select the pier stems to be constructed at this stage. Multiple stems can be selected for simultaneous construction.

**Self Weight Factor:** Factor applied to the pier stems' own weight during this construction stage. A value of `1.0` applies the full self-weight; values greater than `1.0` scale it up and values less than `1.0` reduce it proportionally, which is useful for simulating partial loading scenarios during construction.


---

# 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/construction-tb/substructure-construction-tb/pier-stem-construction-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.