> 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-tub-girder-bridge-ex1-stg/reports-ex1-stg/girder-camber-diagram-and-fabrication-model-ex1-stg.md).

# Girder Camber Diagram and Fabrication Model

**Step 1:** Camber diagram is used in construction, which indicates the specified **camber at all points along the length** of a truss or beam.

When constructing a structure, such as a bridge, fabrication models should be created that take into account displacements made along a line and their corresponding opposite shifts.

This section will cover to create the **Camber Diagram and Fabrication Model** Report by making the required assignments.

**Step 2:** Navigate to Reports > **Girder Camber Diagram and Fabrication Model**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169733160/image-20230228-134403.png?api=v2)

**Step 3:** Set Girder under **Girder Column** to create **Camber Diagram and Fabrication** report.

Set Girder as **G1**.

**Step 4:** Navigate **Deflection Results Cases** tab.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169733160/image-20230228-135144.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2169733160/image-20230228-135348.png?api=v2)

**Step 5:** Click **three-dots icon** on **Steel Dead Load** and click select.

Select **TubGirderDL** in the combobox.

**Step 6:** Repeat the same steps from 4 to 5 for **Non-Composite Dead Load** and **Composite Dead Load**.

Enter data as follows:

* Non-Composite Dead Load: **DeckDL**
* Composite Dead Load: **DC2**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169733160/image-20230228-140516.png?api=v2)

***

{% hint style="success" %}
The Girder Camber Diagram and Fabrication Model have been created.
{% endhint %}

***

If icon won't appear, collapse page tree menu by clicking on arrow or using shortcut "\[".

| **Girder Camber Diagram and Fabrication Model**      |                         |
| ---------------------------------------------------- | ----------------------- |
| General                                              | Deflection Result Cases |
| \`\`\`                                               |                         |
| STGC1 G1                                             |                         |
| \`\`\`                                               | \`\`\`                  |
| STGC1 TubGirderDL DeckDL DC2 Ten Segment per Span NO |                         |

```|
```


---

# 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/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/reports-ex1-stg/girder-camber-diagram-and-fabrication-model-ex1-stg.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.
