> 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-prestressed-i-girder-concrete-bridge-ex1-pig/superstructure-attachments-ex1-pig/custom-barrier-ex1-pig.md).
# Custom Barrier
This section defines custom barriers using user-defined sections for the left side of the deck.
{% hint style="info" %}
**Navigation:** Superstructure Attachments > Custom Barrier
For detailed parameter explanations, see the [Custom Barrier Reference](https://docs.openbrim.org/templates/precast-i-girder-bridge-workflow/superstructure-attachments-pig/barrier-pig).
{% endhint %}
## Steps
### Step 1: Navigate to Custom Barrier
Navigate to **Superstructure Attachments > Custom Barrier** in the tree view.
### Step 2: Select Deck
Click the **three-dots icon** on the **Deck** cell and select **Span1**.
### Step 3: Assign Section
Select the **Exist\_Barrier\_sw** section that was defined in the Properties section.
### Step 4: Set Transverse Location
Enter **Start Transverse Location** and **End Transverse Location** as **-160.43** (for left side placement).
### Step 5: Name the Barrier
Enter the name as **CustBar1**.
### Step 6: Create Barriers for All Spans
Repeat the previous steps to create custom barriers for Span2 and Span3.
Quick Tip: Transverse Offset Direction
Offset values use the Profile Grade Line (PGL) as the reference point.
## Verification
{% hint style="success" %}
After completing these steps, your custom barrier configuration should match the views 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 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-prestressed-i-girder-concrete-bridge-ex1-pig/superstructure-attachments-ex1-pig/custom-barrier-ex1-pig.md?ask=&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.