> 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/spliced-i-girder-bridge-workflow/substructure-code-check-spig/beam-ledges-code-check-spig.md).

# Beam Ledges Code Check \[SPIG]

## Beam Ledges Code Check \[CUG]

## General

**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.

**Select Object:** Select a pier cap object to run beam ledge code checks on.

**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.

## Section Inputs

**Distance from bearing center to cap face:** Horizontal distance from the centerline of the bearing to the front face of the pier cap. Used as the shear span `av` in beam-ledge strength calculations.

**Bracket Height:**

**The width of the inverted T-beam stem:** Width of the inverted T-beam stem, used as `bw` in the shear capacity equations.

**The Width of Inverted T-Beam Stem:**

**Concrete Cover:**

## Reinforcement Inputs

**Primary Reinforcement:**

**Hanger Reinforcement:**

**Reinforcement Spacings:**

**Tie-Stirrup Reinforcement:**

**Number of legs for ties reinforcement:**

**Rebar Material:**

## Bearing Inputs

**Bearing Width (Transverse):**

**Bearing Length (Longitudinal):**


---

# 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/templates/spliced-i-girder-bridge-workflow/substructure-code-check-spig/beam-ledges-code-check-spig.md?ask=<question>&goal=<endgoal>
```

`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.