> 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/support-lines-ex1-cug.md).
# Support Lines
This section defines support line locations for abutments, piers, and temporary supports along the bridge alignment.
{% hint style="info" %}
**Navigation:** Bridge Geometry > Support Lines
For detailed parameter explanations, see the [Support Lines Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/bridge-geometry-cug/support-lines-cug).
{% endhint %}
## Steps
### Step 1: Navigate to Support Lines
Navigate to **Bridge Geometry > Support Lines** in the tree view.
### Step 2: Create End Bent Support Line
Click the **three-dots icon** on the first cell of Bridge and select **Bridge1**.
Set the station to **0 ft** for the first end bent location (Abut1).
### Step 3: Create Pier and Abutment Support Lines
Create support lines for the remaining permanent structures:
| Name | Station |
| ----- | ------- |
| Abut1 | 0 ft |
| Pier1 | 150 ft |
| Pier2 | 300 ft |
| Abut2 | 450 ft |
### Step 4: Add Temporary Support Lines
The permanent support lines are designated for End Bent and Pier Cap locations. Now add Temporary Support locations for sequential assembly of Girder Segments.
Enter the names and stations for all Temporary Supports as shown.
### Step 5: Verify Skew and Offset
Confirm that support lines have no **Skew Angles** or **Transverse Offsets** for this example.
Quick Tip: Transverse Offset Direction
Offset values use PGL (Profile Grade Line) as the reference point.
## Verification
{% hint style="success" %}
After completing these steps, the support lines 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/support-lines-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.