> 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/templates-for-code-check-and-load-rating-ex1-sig/steel-i-girder-code-check-template-ex1-sig.md).
# Steel I Girder Code Check Template
{% hint style="info" %}
**Navigation:** Templates For Code Check And Load Rating > Steel I Girder Code Check Template
For detailed parameter explanations, see the [Steel I Girder Code Check Template Reference](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-sig/steel-i-girder-code-check-t-sig).
{% endhint %}
**Step 1:** Click on Name cell and set name as **SuperstrCCT**.
**Step 2:** As a result of these operations, an issue will appear on the OpenBrIM screen. This does not necessarily mean that any operation was done incorrectly. The issue will be resolved when the load combination table is define in the next step.
Quick Tip: Learn how to read issues
When encountering the warning as seen in OpenBrIM app, there is a "issue" , it is advised to review the parameters you have provided. This warning suggests that there might be a missing or incorrect parameter in your input. Check inputs to ensure they are accurate and complete.
When a warning is clicked, the reason can be displayed. The warning is expressed in the format of Component Group Name (can be viewed in the treeview) > User Defined Component Name (can be viewed in the spreadsheet name column) > Parameter Name (can be viewed in the spreadsheet column header).
After clicking on 'Superstructure > Connections > Bolted Field Splice' in the tree view, navigate to the Bolt category. Set the Bolt Property input. The issue will be resolved after these steps.
The screenshot demonstrates one example of two Bolted Field Splice components named BFS1 and BFS2 by the user, with parameter names **Flange Bolt Property** and **Web Bolt Property**.
**Step 3:** Click the **three-dots icon** on the **Load Combination Table** cell, and then set **SuperstructureLCT**.
**Step 4:** Keep the **Check for, Include Haunch for Properties?, Mlat Comp. Method, Select State Provisions, Type of Construction** as default.
**Step 5:** You can edit the Fatigue parameters of Steel I Girder Code Check from **Fatigue Parameters** tab.
Enter the **ADTT** as **1250.**
Enter the **Number of Lanes Available to Trucks** as **3.**
**Step 6:** Keep the **Ductility parameters ,Appendix A6 parameters,Appendix B6 parameters** as default.
**Step 7:** Go to **Deflection** tab as default.
Define the **Deflection Result Case** with the option '**User Input**.'
Then, choose the **Deflection Result Case** as '**LLDefCase**,' keeping all other parameters set to their default values.
{% hint style="success" %}
The completed steel i girder code check template is 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 %}
{% hint style="success" %}
To view the entire procedure explained on this page, please watch the recorded Video below.
{% endhint %}
{% embed url="" %}
Steel I Girder Code Check
{% 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 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-i-girder-bridge-ex1-sig/templates-for-code-check-and-load-rating-ex1-sig/steel-i-girder-code-check-template-ex1-sig.md?ask=&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.