> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/construction-ex1-cug/superstructure-construction-ex1-cug/temporary-support-construction-ex1-cug.md).

# Temporary Support Construction

This section assigns temporary supports to construction stages, including activation and removal.

{% hint style="info" %}
**Navigation:** Construction > Superstructure Construction > Temporary Support Construction

For detailed parameter explanations, see the [Temporary Support Construction Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/construction-cug/superstructure-construction-cug/temporary-support-construction-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Temporary Support Construction

Navigate to **Construction > Superstructure Construction > Temporary Support Construction** in the tree view.

### Step 2: Assign Activation Stages

Associate temporary supports with the stages when they become active.

### Step 3: Define Removal Stages

Specify the stages when temporary supports are removed after girder continuity is established.

### Step 4: Handle Fixity Changes

For supports with changing fixity conditions, assign the appropriate support definitions (fixed vs. free) to different stages.

## Verification

{% hint style="success" %}
After completing these steps, temporary support staging is defined for the segmental erection sequence.
{% endhint %}


---

# 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/construction-ex1-cug/superstructure-construction-ex1-cug/temporary-support-construction-ex1-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.