> 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-tub-girder-bridge-ex1-stg/templates-for-code-check-ex1-stg/field-splice-code-check-t-ex1-stg.md).

# Field Splice Code Check T

**Step 1:** Navigate Templates for Code Check > **Field Splice Code Check**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995280/image-20230227-112419.png?api=v2)

**Step 2:** For **Internal Cross Frame code check**, 1 Load Combination Tables must be defined.

**Step 3:** Click **three-dots icon** on **Load Combination Table** and set **SuperstructureLCT.**

Since the Field Splice is a superstructure element, the appropriate Load Combination Table to assign would be **"SuperstructureLCT".**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995280/image-20230227-112737.png?api=v2)

**Step 4:** Navigate to **Bridge Parameters** tab.

You can make adjustments to the **"Design Parameters"** tab if you wish.

Keep the "**Design Parameters"** as default (60 kip/in2) for this case.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995280/image-20230227-113045.png?api=v2)

***

{% hint style="success" %}
The Field Splice Code Check have been created.
{% endhint %}

***

If icon won't appear, collapse page tree menu by clicking on arrow or using shortcut "\[".

| **Field Splice Code Check** |                   |
| --------------------------- | ----------------- |
| Params                      | Design Parameters |
| \`\`\`                      |                   |
| FSCCTTG1 SuperstructureLCT  |                   |
| \`\`\`                      | \`\`\`            |
| FSCCTTG1 60                 |                   |

```|
```


---

# 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-tub-girder-bridge-ex1-stg/templates-for-code-check-ex1-stg/field-splice-code-check-t-ex1-stg.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.
