> 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.
### 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).
### 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.
### Step 4: Set Transverse Offsets
Enter **Transverse Offset** values of **-12 ft** and **+12 ft** to position the insertion points on each support line.
### Step 5: Create Remaining Insertion Points
Repeat the process to create insertion points for all support lines with their respective transverse offset values.
Quick Tip: Transverse Offset Direction
Offset values use PGL (Profile Grade Line) as the reference point.
Quick Tip: Skew Angle and Offset Calculation
## Verification
{% hint style="success" %}
After completing these steps, the insertion point layout should appear as shown below.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.openbrim.org/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/bridge-geometry-ex1-cug/insertion-point-ex1-cug.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.