> 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/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/superstructure-attachments-ex1-sig.md).

# 5. Superstructure Attachments

This section covers non-structural elements attached to the bridge deck, including barriers and roadway surfaces.

{% hint style="info" %}
Superstructure attachments contribute to dead load and may affect live load distribution. Define these after the deck is modeled.
{% endhint %}

## Attachments to Model

| Attachment                                                                                                                             | Description                              |
| -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| [Barrier](broken://pages/awz4yxtbvm6V9rXoUbUH)                                                                                         | Traffic barriers along deck edges        |
| [Roadway](/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/superstructure-attachments-ex1-sig/roadway-ex1-sig.md) | Roadway surface and striping definitions |

## Components

* **Barriers**: Concrete traffic barriers (F-shape or similar) that provide vehicle containment
* **Roadway**: Lane markings and surface definitions for load application

## Model Views

![Barrier Placement](https://openbrim.atlassian.net/wiki/download/attachments/2105671690/image-20250117-135851.png?api=v2)

![Complete Deck with Attachments](https://openbrim.atlassian.net/wiki/download/attachments/2105671690/image-20250117-135956.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 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/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/superstructure-attachments-ex1-sig.md?ask=<question>&goal=<endgoal>
```

`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.