> 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/combinations-ex1-sig/design-load-combinations-ex1-sig/load-combination-table-ex1-sig.md).

# Load Combination Table

{% hint style="info" %}
**Navigation:** Combinations > Design Load Combinations > Load Combination Table

For detailed parameter explanations, see the [Load Combination Table Reference](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/combinations-sig/design-load-combinations-sig/load-combination-table-sig).
{% endhint %}

**Step 1:** Click on Name cell and set name as **SuperstructureLCT**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2126282753/image-20231027-140431.png?api=v2)

**Step 2:** Click **three-dots icon** on Strength I cell and select a **Limit State** as **StrengthI.**

If you have reached this stage and you don't have a limit state to select, and if you want to use the **Import Button**, you can refer to the **Quick Tip**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2126282753/image-20231027-140543.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2126282753/image-20231027-140609.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2126282753/image-20231027-140636.png?api=v2)

<details>

<summary><strong>Quick Tip:</strong> Learn how to import limit states</summary>

If there is no limit state to be set, follow the steps below:

\- Click the three dots on the cell and select Import OBPAASHTOLimitState.

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20231027-142307.png?api=v2)

\- In the opened window, choose the limit state.\
\- Click the Import button.

![](https://openbrim.atlassian.net/wiki/download/attachments/2278031376/image-20231027-142445.png?api=v2)

</details>

{% hint style="success" %}
The completed load combination tables are illustrated below. Please verify that you have the same model on your end by examining each view provided here. For more information on how to perform visual checks, refer to the quick tips.
{% endhint %}

![](https://openbrim.atlassian.net/wiki/download/attachments/2126282753/image-20231027-141320.png?api=v2)

{% hint style="success" %}
To view the entire procedure explained on this page, please watch the recorded Video below.
{% endhint %}

{% embed url="<https://openbrim.atlassian.net/wiki/download/attachments/2126282753/Load%20Comb%20Table.mp4?api=v2>" %}
Load Comb Table
{% endembed %}


---

# 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/combinations-ex1-sig/design-load-combinations-ex1-sig/load-combination-table-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.
