> 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/superstructure-code-check-spig/concrete-girder-code-check-spig.md).

# Concrete Girder Code Check \[SPIG]

## Concrete Girder Code Check

### General

**Code Check Template**: This parameter can be used to specify the code check template to be used for the girder’s code check. A previously defined code check template can be assigned using this parameter.

**Girder**: Specify the girder for which the code check will be performed.

**Design Section w Rebars(or Tendons)\[Override Section/Section from 3D]:** Users can specify whether the code check will be performed according to the section that is visible in 3D or if a new section will be overridden to perform code checks accordingly.

**Override Design Section (Noncomposite)**: If the "Design Section w Rebars (or Tendons)" parameter is defined with the option "Override Section," the new section definition can be made using this parameter. The section that will override a previously defined one can be assigned from a previously defined section under Properties > Sections or can be imported. Otherwise, if the "Design Section w Rebars (Tendons)" parameter is defined with the option "Section from 3D," this parameter will not be applicable.

**Stages and Combinations for Girder Stress Checks:** Map the construction stages (and associated load combinations) at which the girder's concrete and tendon stresses are verified. This table is used when the girder's prestress stresses are taken from the FEA. Each row couples a stage or load combination, picked in the **Stage or Combination** column, with the loss time frame and stress limit options described under *Stages for Stress Checks* below.

**Stages for Stress Checks:** Lists the construction stages at which the girder's tendon and concrete stresses are checked, one row per stage. This table is used when the prestress stresses are calculated from the strand geometry in the section rather than taken from the FEA, and the code check template uses the Refined time-dependent loss method. With the Approximate method the table is not used, and the stresses are checked once, at a single final stage after all losses. At least one stage must be assigned to each of the three loss time frames, and every stage in the table must have a day defined.

**Stage:** The construction stage at which the stresses are checked, picked from the project's Construction Stage objects. The stage's day sets the concrete age used in the time-dependent loss calculation.

**Loss Computation Time Frame \[Segment Erection/Between Transfer and Deck Placement/After Deck Placement]:** Places the stage on the refined loss timeline of AASHTO Article 5.9.3.4 and selects the loads and section used for the stress check.

* **Segment Erection:** the girder at prestress transfer and erection. Losses include elastic shortening only, and stresses come from the prestress and the girder self-weight on the noncomposite section.
* **Between Transfer and Deck Placement:** adds the shrinkage, creep and relaxation losses between transfer and deck placement. Stresses come from the prestress and the girder and deck weight on the noncomposite section, plus superimposed dead loads on the composite section.
* **After Deck Placement:** adds the losses between deck placement and final time, including the gain from deck shrinkage. Stresses are checked on the composite section: compression under Service I and tension under Service III (AASHTO 5.9.2.3.2).

**Tendon Stress Check \[Immediately prior to transfer/At service limit state after all losses/Prior to seating/At anchorages and couplers immediately after anchor set/Elsewhere along length of member away from anchorages and couplers immediately after anchor set/At service limit state after losses]:** The stress limit for the prestressing steel at this stage, from AASHTO Table 5.9.2.2-1. The first two options are for **pretensioned** strands and the last four for **post-tensioned** tendons, so choose from the group that matches how the girder is prestressed. A post-tensioning option has no limit for pretensioned strands: for a girder prestressed with strands only, the report shows a limit of 0 and the check fails. Note that *At service limit state after all losses* (pretensioning) and *At service limit state after losses* (post-tensioning) differ by one word.

The limits below are for low-relaxation strand:

| Option                                                                                          | Prestressing   | Limit               |
| ----------------------------------------------------------------------------------------------- | -------------- | ------------------- |
| Immediately prior to transfer                                                                   | Pretensioned   | 0.75 f<sub>pu</sub> |
| At service limit state after all losses                                                         | Pretensioned   | 0.80 f<sub>py</sub> |
| Prior to seating                                                                                | Post-tensioned | 0.90 f<sub>py</sub> |
| At anchorages and couplers immediately after anchor set                                         | Post-tensioned | 0.70 f<sub>pu</sub> |
| Elsewhere along length of member away from anchorages and couplers immediately after anchor set | Post-tensioned | 0.74 f<sub>pu</sub> |
| At service limit state after losses                                                             | Post-tensioned | 0.80 f<sub>py</sub> |

**Compression Check \[0.65f'ci/0.45f'c/0.6f'c]:** The compressive stress limit for the concrete at this stage.

| Option   | Use for                                                                                               | AASHTO             |
| -------- | ----------------------------------------------------------------------------------------------------- | ------------------ |
| 0.65f'ci | Temporary stresses before losses, at transfer                                                         | 5.9.2.3.1a         |
| 0.45f'c  | Service after losses: effective prestress and permanent loads                                         | Table 5.9.2.3.2a-1 |
| 0.6f'c   | Service after losses: effective prestress, permanent and transient loads (φ<sub>w</sub> taken as 1.0) | Table 5.9.2.3.2a-1 |

**Tensile Stress Limit \[0.0948λ√\*fci/0.24λ√\*fci/0.158λ√\*fci/0.19λ√\*fci/No Tension before Losses/0.19λ√\*fc/0.0948λ√\*fc/No Tension after Losses]:** The tensile stress limit for the concrete at this stage. The first five options are temporary limits before losses, based on f'ci, and are meant for the transfer stage. The last three are service limits after losses, based on f'c. λ is the concrete density modification factor (AASHTO 5.4.2.8).

| Option                   | Limit                  | Use for                                                                                               | AASHTO             |
| ------------------------ | ---------------------- | ----------------------------------------------------------------------------------------------------- | ------------------ |
| 0.0948λ√\*fci            | 0.0948λ√f'ci ≤ 0.2 ksi | Before losses, areas other than the precompressed tensile zone, without bonded reinforcement          | Table 5.9.2.3.1b-1 |
| 0.24λ√\*fci              | 0.24λ√f'ci             | Before losses, areas with bonded reinforcement sufficient to resist the tensile force in the concrete | Table 5.9.2.3.1b-1 |
| 0.158λ√\*fci             | 0.158λ√f'ci            | Before losses, handling stresses in prestressed piles                                                 | Table 5.9.2.3.1b-1 |
| 0.19λ√\*fci              | 0.19λ√f'ci             | Before losses, segmentally constructed bridges, areas with bonded reinforcement                       | Table 5.9.2.3.1b-1 |
| No Tension before Losses | 0                      | Before losses, segmentally constructed bridges, areas without bonded reinforcement                    | Table 5.9.2.3.1b-1 |
| 0.19λ√\*fc               | 0.19λ√f'c ≤ 0.6 ksi    | After losses, bonded tendons or reinforcement, not worse than moderate corrosion conditions           | Table 5.9.2.3.2b-1 |
| 0.0948λ√\*fc             | 0.0948λ√f'c ≤ 0.3 ksi  | After losses, bonded tendons or reinforcement, severe corrosive conditions                            | Table 5.9.2.3.2b-1 |
| No Tension after Losses  | 0                      | After losses, unbonded prestressing tendons                                                           | Table 5.9.2.3.2b-1 |

A typical setup for a pretensioned girder:

| Stage                      | Loss Computation Time Frame         | Tendon Stress Check                     | Compression Check | Tensile Stress Limit                                       |
| -------------------------- | ----------------------------------- | --------------------------------------- | ----------------- | ---------------------------------------------------------- |
| Girder erection (transfer) | Segment Erection                    | Immediately prior to transfer           | 0.65f'ci          | 0.24λ√\*fci, or 0.0948λ√\*fci without bonded reinforcement |
| Deck casting               | Between Transfer and Deck Placement | At service limit state after all losses | 0.45f'c           | 0.19λ√\*fc                                                 |
| Final (service)            | After Deck Placement                | At service limit state after all losses | 0.6f'c            | 0.19λ√\*fc, or 0.0948λ√\*fc in severe corrosive conditions |

**Location Input Method \[Station/Relative on Span/Before Section Change/After Section Change]:** How the check location is given. **Station** takes the station directly. **Relative on Span** takes a span number and a fraction of that span. **Before Section Change** and **After Section Change** place the check just before or just after one of the girder's section changes.

**Station**: This parameter can be used to specify the station at which the code check will be performed. Shown when **Location Input Method** is **Station**.

**Girder Span Number:** The span of the girder the check is in, counted from the girder's start. Shown when **Location Input Method** is **Relative on Span**.

**Relative Position along Span (0-1):** Where the check is in that span: 0 at its start, 0.5 at midspan, 1 at its end. Shown when **Location Input Method** is **Relative on Span**.

**Use CL of Bearings/Piers \[Bearings/Piers/Use the station where the Girder intersects the Pier]:** Which stations bound the spans for **Relative on Span**: the bearings of the girder (the default), the stations of the support lines (the pier centerlines), or the stations where the girder crosses the piers.

**Section Change No:** Which section change of the girder the check is placed at, counted from the girder's start. Shown for **Before Section Change** and **After Section Change**.

**Location Offset:** How far before or after that section change the check is placed. A value of 0 places it just off the section change. Shown for **Before Section Change** and **After Section Change**.

**Resolved Station (readonly)**: The station the code check actually uses, whichever **Location Input Method** gives it.

**Relative Position (readonly)**: The relative position of the code check station based on the total length of the girder will be presented to the user.

**Effective Web Width**:

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

### Shear Reinforcements

**Shear Reinforcement Data \[Use Girder’s Rebar Data/ Override Rebar Data]:** Users can specify whether to use the rebar data previously defined in the girder object or to override the shear reinforcement data with the parameters below for use in code checks.

**Rebar Profile:** If the shear reinforcement data is to be overridden, the rebar profile can be specified using this parameter.

**Rebar Spacing:** This parameter can be used to specify the spacing between rebar elements.

**Number of Legs:** This parameter can be used to define the number of rebar legs in the shear reinforcement.

**Transverse Rebar Material:** This parameter can be used to specify the material used for the shear reinforcement.


---

# 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/spliced-i-girder-bridge-workflow/superstructure-code-check-spig/concrete-girder-code-check-spig.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.
