> 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/cross-frame-code-check-template-ex1-sig.md).
# Cross Frame Code Check Template
{% hint style="info" %}
**Navigation:** Templates For Code Check And Load Rating > Cross Frame Code Check Template
For detailed parameter explanations, see the [Cross Frame Code Check Template Reference](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-sig/cross-frame-code-check-t-sig).
{% endhint %}
**Step 1:** Click on Name cell and set name as **CFrameCCT**.
**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:** Go to the **Fatigue Parameters** tab.
Set **ADTT** to **1250** and **Number of Lanes Available to Trucks** to **3**.
Leave the rest of the parameters as default.
### Step 6
Keep the parameters in the **Tensile Resistance Parameters** tab as default.
{% hint style="success" %}
The completed cross frame 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="" %}
Cross Frame Code Check T
{% 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 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/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/templates-for-code-check-and-load-rating-ex1-sig/cross-frame-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 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.