> 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-tub-girder-bridge-workflow/superstructures-code-check-stg/field-splice-code-check-aashto-stg.md).

# Field Splice Code Check (AASHTO) \[STG]

## Field Splice Code Check (AASHTO) \[STG]

The code check designs a tub girder Bolted Field Splice to AASHTO LRFD 9th Edition Article 6.13.6.1, with the checks the NSBA *Bolted Field Splices for Steel Bridge Flexural Members* recommends. It works on the plates and bolts as they are placed in the splice (its Splice Plates and Splice Bolts tables), and on the girder sections on both sides of the joint. The detailed report has three parts: **Design Parameters**, **Flange Splice Design** and **Web Splice Design**.

The checks are those of the steel I-girder splice: net sections along every chain of holes (6.8.3), block shear on every valid path on both sides of the joint (6.13.4), bearing hole by hole with each hole's clear distance and limited to the bolt shear resistance (6.13.2.9), bolt shear and slip (6.13.2.7, 6.13.2.8), and the detailing measured on the bolts as placed (6.13.2.4.2, 6.13.2.6, 6.7.3). See [Bolted Field Splice Code Check (AASHTO) \[SIG\]](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/superstructure-code-check-sig/bolted-field-splice-code-check-aashto-sig.md) for the report drawings. A tub girder adds:

* **Both top flanges and both webs**, each designed with the plates and bolts the splice gives them; distances on a sloped web are measured along the web (6.11.2.1.1).
* **St. Venant torsional shear of the box** (6.13.6.1.3b, C6.11.1.1). The torque of the governing combination is split by the section it acts on: the factored noncomposite dead load (DC1) torque on the enclosed area of the noncomposite box, the rest on the enclosed area of the composite box, which reaches the mid-thickness of the deck. Where the two girders differ, the smaller enclosed areas are taken. The shear flows give the St. Venant shear V\_SV in the bottom flange.
  * At the strength limit state, the bottom flange splice plates, their bolts and the bearing at the bolt holes are designed for the vector sum of the flange force and V\_SV.
  * At the service limit state, V\_SV is subtracted from the bottom flange force that the web splice carries, and the vertical St. Venant shear in the critical web is added to the web shear in its plane (6.11.9), for the slip check of the web bolts.
  * The template's **St. Venant torsional shear, box sections** turns it off.

![The internal torques of the St. Venant check in the detailed report: the governing torque, the factored DC1 torque on the noncomposite box and the rest on the composite box](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-21e3d7ba2ca53c162a33672de2263d140a8ddede%2Fsplice-code-check-st-venant-torques.png?alt=media)

![The bottom flange design force: the vector sum of the flange force P\_fy and the St. Venant shear V\_SV](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-8cb2b58bfdc2bb85791f0f06f0f3049bac57137c%2Fsplice-code-check-st-venant-design-force.png?alt=media)

Project-wide settings (the limit states, the filler yield strength, block shear U\_bs, the NSBA checks, the St. Venant shear and the web plate design force) are in the Field Splice Code Check template.

## General

**Splice:** Splice for code check

**Code Check Template:** The code check template is utilized to extract global parameters, results from finite element analysis, and limit states employed in the design process.

**PDF Name (Export):** This parameter allows the name of the code check document to be modified when saving it as a PDF. When renaming the file, special attention must be given to the text characters on the [linked](https://docs.openbrim.org/faq/general/faq-illegal-chars) page, as certain characters may interfere with parametric equations and lead to unexpected results.

## Overrides

**Override Transverse Stiffener Spacing \[Yes/No]:** Enables manual input of the transverse stiffener spacing used in the web-shear capacity computations. When YES, the value entered below overrides the auto-computed spacing.

**Transverse Stiffener Spacing:** The user-specified transverse stiffener spacing applied when the override option is active.

**Computed Transverse Stiffener Spacing, Left (readonly):** The transverse stiffener spacing of the left girder at the splice, from the transverse stiffener objects attached to it; used in the web shear resistance of that girder. Shown when the override is off. (Read-only)

**Computed Transverse Stiffener Spacing, Right (readonly):** The same for the right girder. Shown when the override is off. (Read-only)

**Girder Start Station (readonly):** Displays the start station of the girder along the PGL. This value is automatically determined from the girder geometry. (Read-only)

**Girder End Station (readonly):** Displays the end station of the girder along the PGL. This value is automatically determined from the girder geometry. (Read-only)


---

# 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-tub-girder-bridge-workflow/superstructures-code-check-stg/field-splice-code-check-aashto-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.
