> 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-i-girder-bridge-workflow/superstructure-code-check-sig/bolted-field-splice-code-check-aashto-sig.md).

# Bolted Field Splice Code Check (AASHTO) \[SIG]

## Bolted Field Splice Code Check (AASHTO) \[SIG]

The code check designs a 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** (the girders, the plates, the bolts and the analysis results), **Flange Splice Design** and **Web Splice Design**.

![Elevation of the splice in the detailed report: the web plates and their bolts, as the Splice Editor draws them](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-8dc3adb7dffb5b0a916928b7c14eec1c950c0959%2Fsplice-code-check-elevation.png?alt=media)

What the report checks, from the actual bolts and plate edges:

* **Flange design force** (6.13.6.1.3b): the design yield resistance P\_fy of the smaller flange, with its net section along the chain of holes (6.8.3).
* **Net sections** (6.8.3): every chain of holes across the girder flange and across each splice plate, staggered chains included. The report draws the critical net section (Path Mode-1) and the second one (Path Mode-2), for each girder.
* **Block shear rupture** (6.13.4): every valid path on both sides of the joint, for the girder flange and each splice plate; the report draws the two most critical (Mode-1 and Mode-2).
* **Bearing at the bolt holes** (6.13.2.9): hole by hole, each with its own clear distance L\_c to the next hole or to the end of the material, the bearing of a hole limited to the shear resistance of its bolt.
* **Bolts**: shear (6.13.2.7) with the filler reduction (6.13.6.1.4) and slip at the service limit state (6.13.2.8).
* **Detailing** (6.13.2.4.2, 6.13.2.6, 6.7.3): hole size, bolt spacing, edge and end distances, sealing spacing and minimum thicknesses, measured on the bolts as placed.
* **Web splice** (6.13.6.1.3c): the web plates and their bolts for the shear and the horizontal force of the web; the template's **Web splice plate design force** chooses the force the web plates are designed for.

![Critical net section through the girder flange, drawn in the detailed report](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-e4a5b5a6976e3233999ebea447022b5d6ee0a841%2Fsplice-code-check-net-section.png?alt=media)

![Most critical block shear path of the girder flange](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-5beff467e30c38b737f622083d90925a23de01e7%2Fsplice-code-check-block-shear.png?alt=media)

![Clear distance L\_c of each hole toward the girder end; a ring marks a hole whose L\_c is below 2d](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-18660e2fd9c4c2336e1a2cd1f70bd04fadeb1d4c%2Fsplice-code-check-bearing.png?alt=media)

Project-wide settings (the limit states, the filler yield strength, block shear U\_bs, the NSBA checks 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 at the splice. 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-i-girder-bridge-workflow/superstructure-code-check-sig/bolted-field-splice-code-check-aashto-sig.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.
