> 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/superstructure-ex1-cug/temporary-support-ex1-cug/single-elements-ex1-cug.md).

# Single Elements

This section defines temporary support elements for segmental construction of the Concrete U Girders.

{% hint style="info" %}
**Navigation:** Superstructure > Temporary Support > Single Element
{% endhint %}

## Steps

### Step 1: Understand Temporary Support Purpose

When constructing Concrete U Girders over a span, construction is executed in a **segmental** manner due to transportation constraints. Stability issues arise during this process, requiring temporary supports at specific points.

### Step 2: Navigate to Single Element

Navigate to **Temporary Support > Single Element** in the tree view.

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2265022465/image-20230829-140239.png?api=v2)

### Step 3: Select Girder

Click on the **Girders** column and select **CUG1** from the dropdown.

### Step 4: Pick Support Locations

Click **Pick** from the dropdown to select temporary support locations graphically.

![Pick Locations](https://openbrim.atlassian.net/wiki/download/attachments/2265022465/image-20230829-142944.png?api=v2)

Enter the name as **TSupL1** for the first support.

### Step 5: Create Supports for Both Girders

The temporary support locations for **CUG1** also apply to **CUG2** since they are built identically as segmental girders.

![Both Girders](https://openbrim.atlassian.net/wiki/download/attachments/2265022465/image-20230829-143746.png?api=v2)

{% hint style="info" %}
Temporary supports are also used during **closure pour casting** operations of the girders.
{% endhint %}

### Step 6: Define Additional Supports for Fixity Changes

**Temporary Supports 3, 5, 7, and 9** have fixity states that change during construction. These supports are redefined to accommodate the changes (explained in detail on the Construction Stages page).

![Additional Supports](https://openbrim.atlassian.net/wiki/download/attachments/2265022465/image-20230829-150815.png?api=v2)

### Step 7: Configure Fixity Values

Navigate to the **Fixity** spreadsheet.

![Fixity Tab](https://openbrim.atlassian.net/wiki/download/attachments/2265022465/image-20230829-152020.png?api=v2)

Enter the fixity values for each temporary support as shown. The fixity pattern varies based on whether the support needs to resist axial forces during specific construction stages.

## Verification

{% hint style="success" %}
After completing these steps, the temporary supports are defined and ready for use in construction stage definitions.
{% 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/superstructure-ex1-cug/temporary-support-ex1-cug/single-elements-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.