> 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/templates/steel-i-girder-bridge-workflow/loading-sig/loads-sig/temperature-load-sig/uniform-temperature-load-sig.md).

# Temperature Load \[SIG]

## General

Normally, two distinct scenarios should be generated with two stages for contraction and expansion. The AASHTO gradient also has two, a positive and a negative one.

**Bridge:** Choose the bridge to automatically apply the temperature load on all deck and girder components.

**Applied Elements \[Superstructure/Superstructure and Substructure]:** Selects which parts of the bridge receive the temperature change. Superstructure applies it to the deck and girder components only; Superstructure and Substructure also applies it to the piers, columns, and other substructure elements. With AASHTO Gradient, the substructure takes the uniform temperature calculated below, and only the deck takes the gradient.

**Stage:** Choose a stage to apply the temperature loading. AASHTO Gradient needs a stage, because without one the load is not applied in a staged model.

**Temperature Type \[Uniform/AASHTO Gradient]:** Uniform applies one temperature change to everything selected. AASHTO Gradient applies the vertical temperature gradient of AASHTO LRFD Article 3.12.3 for steel superstructures, with the dimension A taken as 12 in., T3 as 0 and t as the deck thickness.

AASHTO Gradient is available only when every girder on the bridge is a steel I-girder, or an arbitrary section girder with a steel material. Other girder types, steel tub girders included, are refused with a message. The deck must be at least 4 in. thick, and every deck and girder material needs a thermal coefficient.

**Temperature Change From Mean:** When dealing with expansion, it is necessary to input a positive temperature value, whereas a negative temperature value should be utilized for contraction. Shown when the temperature type is Uniform.

**T1, Top of Deck:** The temperature at the top of the deck. Shown when the temperature type is AASHTO Gradient.

**T2, 4 in. Below Top of Deck:** The temperature 4 in. below the top of the deck. Shown when the temperature type is AASHTO Gradient.

Take the positive values of T1 and T2 from AASHTO LRFD Table 3.12.3-1, for the bridge's solar radiation zone in Figure 3.12.3-1. For the negative gradient, multiply both by −0.30 for a plain concrete deck or −0.20 for a deck with an asphalt overlay.

| Zone | T1 (°F) | T2 (°F) |
| ---- | ------- | ------- |
| 1    | 54      | 14      |
| 2    | 46      | 12      |
| 3    | 41      | 11      |
| 4    | 38      | 9       |

**Uniform Temperature, Except Deck:** The temperature applied to everything other than the deck, such as girders, cross-frames, diaphragms and barriers. It is the gradient's value at the bottom of the deck, T2 × (16 − t) / 12, and 0 for a deck 16 in. or thicker. AASHTO does not define a gradient for barriers, so taking this value for them is an assumption. If the deck thickness varies, this value uses the first thickness of the first deck. (Read-only)

**Apply to Rigid Elements \[No/Yes]:** Selects whether rigid elements, such as rigid links, also receive the temperature load.

{% hint style="info" %}
**How the deck takes the gradient**

A deck shell can only hold a straight line of temperature through its thickness, and the AASHTO profile has a break at 4 in. Each deck shell therefore takes the straight line with the same axial force and moment as the profile, for its own thickness to the nearest 0.5 in. Reactions, deflections and member forces are not affected by this. The self-balancing internal stresses of the profile are not included in the results.

For example, with T1 = 54, T2 = 14 and an 8 in. deck, the deck takes 45.17 °F at its top and 0.50 °F at its bottom, and everything else takes 9.33 °F.
{% endhint %}

{% hint style="info" %}
**Setting up the AASHTO gradient**

1. In **Construction Stage**, add two stages. Give both the same **Prior Stage**, usually the last dead load stage, and set **Load Type** to Temperature. Use the same settings as the bridge's other temperature stages, such as **Composite Section**. Sharing a prior stage keeps the two gradients apart from each other and from later stages.
2. Add two of these temperature loads, one on each stage, with **Temperature Type** set to AASHTO Gradient. Enter the positive T1 and T2 on one and the negative values on the other.
3. In **Result Extraction (From Stages)**, add one object with both stages in **Stages | Factors** at a factor of 1. Set **Filter by Load Type** to Temperature and **Combination Method** to Envelope (Critical).
4. In **Limit States**, select that object under **TG (Temperature Gradient)**, and check **γ max** and **γ min** on every limit state. Each limit state must also be selected in the **Load Combination Table** to produce a combination.

AASHTO LRFD Article 3.4.1 says the load factor should be considered on a project-specific basis. In lieu of project-specific information, it may be taken as 0.0 at the strength and extreme event limit states, 1.0 at the service limit state when live load is not considered, and 0.50 at the service limit state when live load is considered.
{% endhint %}

{% hint style="info" %}
**Reading the effect on bearings and substructure**

The gradient redistributes reactions along and across the bridge, which AASHTO LRFD C3.12.3 says should be considered in the design of the bearings and substructures. The regular analysis results show this. Read the result extraction object from step 3 to see the gradient alone, since a stage's own results also include everything built up to that stage.

The reactions over the whole bridge sum to about zero, but individual bearings can change by a large amount. Where all the bearings on a line restrain the same direction, each can carry a large force even when the total across the line is small.
{% 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/templates/steel-i-girder-bridge-workflow/loading-sig/loads-sig/temperature-load-sig/uniform-temperature-load-sig.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.
