> 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-concrete-u-girder-bridge/load-rating-ex1-cug/girder-load-rating-ex1-cug.md).

# Girder Load Rating

This section performs load rating analysis for the U-girder superstructure.

{% hint style="info" %}
**Navigation:** Load Rating > Girder Load Rating

For detailed parameter explanations, see the [Girder Load Rating Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/load-rating-cug/concrete-girder-load-rating-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Girder Load Rating

Navigate to **Load Rating > Girder Load Rating** in the tree view.

### Step 2: Select Rating Template

Associate the appropriate load rating code check template configured earlier.

### Step 3: Configure Rating Parameters

Set rating analysis parameters:

* **Rating Vehicle:** Select from HL-93, legal loads, or permit vehicles
* **Rating Level:** Design, Legal, or Permit
* **Condition Factor:** Based on structural condition assessment

### Step 4: Define Check Locations

Specify sections for rating factor calculation:

* Critical moment locations
* Critical shear locations
* Tendon stress zones

### Step 5: Run Load Rating

Execute the load rating analysis and review rating factors.

<details>

<summary><strong>Quick Tip:</strong> Rating Factor Interpretation</summary>

A rating factor (RF) ≥ 1.0 indicates adequate capacity for the rating vehicle. RF < 1.0 indicates the structure cannot safely carry the rated load.

</details>

## Verification

{% hint style="success" %}
After completing these steps, review the rating factors to confirm adequate load-carrying capacity.
{% 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-concrete-u-girder-bridge/load-rating-ex1-cug/girder-load-rating-ex1-cug.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.