> 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-prestressed-i-girder-concrete-bridge-ex1-pig/templates-for-code-check-and-load-rating-ex1-pig/prestressed-i-girder-code-check-t-ex1-pig.md).

# Prestressed I Girder Code Check T

This section creates code check templates for prestressed I girders, defining load combinations and analysis parameters for strength, service, and fatigue limit state checks.

{% hint style="info" %}
**Navigation:** Templates for Code Check and Load Rating > Prestressed I Girder Code Check

For detailed parameter explanations, see the [Prestressed I Girder Code Check Template Reference](https://docs.openbrim.org/templates/precast-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-pig/concrete-girder-code-check-pig).
{% endhint %}

## Overview

Multiple code check templates can be defined for different limit states and design scenarios. Each template specifies load combinations and verification settings.

## Steps

### Step 1: Navigate to Prestressed I Girder Code Check Template

Navigate to **Templates for Code Check and Load Rating > Prestressed I Girder Code Check** in the tree view.

![Navigation](https://openbrim.atlassian.net/wiki/download/attachments/2235400506/image-20230731-084541.png?api=v2)

### Step 2: Create Template

Enter the name **PIGTemp** in the Name column.

### Step 3: Assign Load Case for Girder Weight

Click the **three-dots icon** on **Load Case of Girder Weight Only** and select **DC1** (dead load).

![Load Case Selection](https://openbrim.atlassian.net/wiki/download/attachments/2235400506/image-20230731-084848.png?api=v2)

### Step 4: Assign Load Combination Table

Click the **three-dots icon** on **Load Combination Table** and assign **SuperstructureLCT**.

{% hint style="info" %}
Since I-girders are part of the superstructure, use the superstructure load combination table.
{% endhint %}

![Load Combination Assignment](https://openbrim.atlassian.net/wiki/download/attachments/2235400506/image-20230731-085911.png?api=v2)

### Step 5: Keep Default Parameters

Maintain all other parameters at their default values.

![Default Parameters](https://openbrim.atlassian.net/wiki/download/attachments/2235400506/image-20230731-090224.png?api=v2)

### Step 6: Configure Section Property Tab

Navigate to the **Section Property** tab and set parameters as shown.

![Section Property Tab](https://openbrim.atlassian.net/wiki/download/attachments/2235400506/image-20230731-090521.png?api=v2)

## Verification

{% hint style="success" %}
After completing these steps, the Prestressed I Girder Code Check template is ready for use.
{% 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 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/concrete-bridge-examples/example-prestressed-i-girder-concrete-bridge-ex1-pig/templates-for-code-check-and-load-rating-ex1-pig/prestressed-i-girder-code-check-t-ex1-pig.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.