> 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/bridge-geometry-ex1-cug/insertion-point-ex1-cug.md).

# Insertion Point

This section defines insertion points that position U-girders along each support line.

{% hint style="info" %}
**Navigation:** Bridge Geometry > Insertion Point

For detailed parameter explanations, see the [Insertion Point Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/bridge-geometry-cug/insertion-point-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Insertion Point

Navigate to **Bridge Geometry > Insertion Point** in the tree view.

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230824-090250.png?api=v2)

### Step 2: Create First Insertion Point

Click the **three-dots icon** on the first cell of Location and select **Select**.

From the dropdown menu, choose **SL1** (support line for End Bent location).

![Select Support Line](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230824-090458.png?api=v2)

### Step 3: Plan Insertion Points

For each support line, create one insertion point beneath each Concrete U Girder.

Since there are two U-girders in this project, there will be two insertion points on each support line.

![Insertion Point Layout](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230824-111639.png?api=v2)

### Step 4: Set Transverse Offsets

Enter **Transverse Offset** values of **-12 ft** and **+12 ft** to position the insertion points on each support line.

![Transverse Offset](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230824-112310.png?api=v2)

### Step 5: Create Remaining Insertion Points

Repeat the process to create insertion points for all support lines with their respective transverse offset values.

<details>

<summary><strong>Quick Tip:</strong> Transverse Offset Direction</summary>

Offset values use PGL (Profile Grade Line) as the reference point.

![Offset Direction](https://openbrim.atlassian.net/wiki/download/attachments/2104689432/image-20230216-130246.png?api=v2)

</details>

<details>

<summary><strong>Quick Tip:</strong> Skew Angle and Offset Calculation</summary>

![Skew Calculation](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230216-140820.png?api=v2)

![Offset Calculation](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230216-141049.png?api=v2)

</details>

## Verification

{% hint style="success" %}
After completing these steps, the insertion point layout should appear as shown below.
{% endhint %}

![Completed Insertion Points](https://openbrim.atlassian.net/wiki/download/attachments/2258665474/image-20230824-112600.png?api=v2)


---

# 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/bridge-geometry-ex1-cug/insertion-point-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.
