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

# Construction \[TB]

Staged-Based Analysis is a crucial analytical feature available in OpenBrIM, designed to simulate and evaluate the structural behavior of bridges throughout their construction phases. This analysis enables engineers to assess how various construction stages impact the overall performance and stability of the bridge.

To effectively conduct Staged-Based Analysis, it is essential to:

1. **Define Construction Stages**: Clearly outline each phase of the construction process, identifying the sequence of activities and specific conditions that apply at each stage.
2. **Assign Bridge Elements**: For each defined construction stage, assign the relevant bridge elements to either construction or deconstruction. This ensures that the analysis accurately reflects how each element contributes to the bridge's structural integrity during different phases.

For a truss bridge, the workflow adds dedicated construction/deconstruction objects for truss members, truss cables, and arch elements on top of the standard superstructure, cable-element, and substructure staging.

For a comprehensive description of each section related to this part of the workflow, please refer to the corresponding documentation page.


---

# 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.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.