> 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-segmental-bridge-workflow/construction-cbs/substructure-construction-cbs/foundation-partial-cbs.md).

# Foundation (Partial) \[CBS]

If a footing is built in two connected stages, such as the first stage being associated with an existing structure constructed 20 years ago and the second stage involving the addition of a new part to the footing for a rehabilitation project, this object can be used to simulate the behavior. If the footings are not connected, two separate footings can be constructed in two different stages.

**Stage:** Choose the stage for constructing the footings.

**Foundation:** Choose the footings for construction.

**Start Station (From Right):** When determining stations in the direction of PGL, starting from the right, specify the start station of the foundation to be constructed.

**End Station (From Right):** When determining stations in the direction of PGL, starting from the right, specify the end station of the foundation to be constructed.

**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).


---

# 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-segmental-bridge-workflow/construction-cbs/substructure-construction-cbs/foundation-partial-cbs.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.