> 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/concrete-u-girder-bridge-workflow/construction-cug/substructure-construction-cug/pier-cap-end-bent-construction-complete-cug.md).

# Pier Cap/Bent Construction (Complete) \[CUG]

## Pier Cap Construction

If a pier cap is to be partially constructed and the user aims to check for the creep and shrinkage effects of each deck pour, they can use the pier cap/bent (partial) construction section.

**Stage:** Choose the stage for constructing the pier or bents. Usually, the construction of pier caps, piers, footings, and piles is completed within a single stage.

**Pier Caps/Bents:** Choose the pier caps or bents for construction.

**Self-Weight Factor**: The Self-Weight Factor is a parameter used to adjust the contribution of an object's own weight in structural analysis. This factor is particularly useful in simulations, as it enables the scaling or modification of the self-weight during finite element analysis (FEA).

**Pier Cap Construction Method \[Weight only/Stiffness only/Weight and Stiffness]:** Determines how the pier cap is modeled during construction:

* **Weight only:** Applies self-weight without structural stiffness contribution.
* **Stiffness only:** Provides structural stiffness without self-weight contribution.
* **Weight and Stiffness:** Applies both self-weight and full stiffness contribution (default).


---

# 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/concrete-u-girder-bridge-workflow/construction-cug/substructure-construction-cug/pier-cap-end-bent-construction-complete-cug.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.