> 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/combinations-ex1-stg/design-load-combinations-ex1-stg/load-combination-table-ex1-stg.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-tub-girder-bridge-workflow/combinations-stg/design-load-combinations-stg/load-combination-table-stg).
{% endhint %}

**Step 1:** This section aims to compile the limit states that were previously defined based on AASHTO guidelines. Each limit state input generates two core combination objects (Max/Min), and overall limit state envelopes are produced for strength, service, fatigue, and extreme event limit states. Additionally, you need to **create** three **Load Combination Tables** for the **Substructure**, **Superstructure**, and **Superstructure Constructibility** categories.

**Step 2:** Navigate to Combinations > Design Load Combinations > **Load Combination Table**

![](https://openbrim.atlassian.net/wiki/download/attachments/2170224641/image-20230227-075400.png?api=v2)

**Step 3:** Enter the name in the **Name** column as follows:

* SubstructureLCT
* SuperstructureLCT
* SuperStrConstLCT

**Step 4:** Click **three-dots icon** on **StrengthI** 1st Row Cell and click **Select.**

![](https://openbrim.atlassian.net/wiki/download/attachments/2170224641/image-20230227-075626.png?api=v2)

**Step 5:** Select **StrengthI\_sub** from the combobox.

![](https://openbrim.atlassian.net/wiki/download/attachments/2170224641/image-20230227-080020.png?api=v2)

**Step 6:** Select the suitable **StrengthI** options for **SuperstructureLCT** and **SuperStrConstLCT**, based on the instructions provided in the previous step.

![](https://openbrim.atlassian.net/wiki/download/attachments/2170224641/image-20230227-080931.png?api=v2)

**Step 7:** In same way, keep selecting Limit States for the corresponding **Load Combination Tables**.

Limit States not included in this example should remain as **NULL**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2170224641/image-20230227-081815.png?api=v2)

***

{% hint style="success" %}
The Load Combination Table have been created using limit states.
{% endhint %}

***

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


---

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