# Steel I Girder Code Check T \[SIG] ## General **Load Combination Table:** The load combination table is used to map the analysis result cases and their corresponding factors to the template, along with the limit states. It serves as the basis for all finite element analysis results used in the code check equations. **Check For \[Constructibility/StrengthServiceFatigue]:** The code check component only allows for either a constructibility or a strength-service-fatigue limit state check in a single run. Therefore, if the user intends to perform a constructibility check, the finite element results that need to be mapped will likely differ significantly from those required for a strength-service-fatigue limit state check. **Include Haunch for Section Properties? \[Yes/No]:** According to DOT requirements, haunch area may or may not be included in the sectional property computations. When haunch is included, it increases the inertia and section modulus and decreases the stress values, making the calculation less conservative. When set to NO, the dimensions of the haunch are still used to determine the locations of the deck and girder sections. **Mlat Comp. Method \[FEA/AASHTO Eqn C4.6.1.2.4b.1/Envelope of FEA and AASHTO Eqn]:** If the user selects the FEA option, the lateral bending moments are calculated using finite element analysis. The OpenBrIM model divides the steel I-girder into three finite elements, using a beam for the top and bottom flanges and a shell for the web. If the AASHTO equation is selected, the major-axis bending moment is converted to lateral bending per AASHTO C4.6.1.2.4b. The Envelope option selects the larger value between the FEA and AASHTO equation results. **Select State Provisions:** In cases where additional code checks are needed based on state provisions, this parameter can be used to specify the required state provision. **Type of Construction \[Shored\_Construction/Unshored\_Construction]:** For steel I-girder bridges, **unshored** construction is commonly employed. In this method, any permanent load applied before the concrete deck has hardened or become composite is assumed to be borne entirely by the steel section, while any permanent load and live load applied after this stage are assumed to be supported by the composite section. In the case of shored construction, all permanent load is assumed to be applied after the concrete deck has hardened or become composite, and this information should be clearly stated in the contract documents. **Support Lines for Span Definition \[All/Selection]:** Specifies the support lines to be used in span definition. **'All'** includes all support lines associated with the girder. **'Selection'** allows manual selection of support lines for span computation. **Selected Support Lines :** Specifies the support lines to be considered in span computation when **'Selection'** is selected in the *Support Lines for Span Definitions* input. Only the selected support lines will be used to define spans. **Use Deck Rebar in Plastic Mom. Calc. (Pos. Flex.) \[Yes/No]:** This parameter controls whether deck reinforcement is included when calculating the plastic moment capacity for positive flexure regions. When set to YES, the deck rebar contributes to the plastic moment capacity calculation. ## Fatigue Parameters **Detail Category (Table 6.6.1.2.3-1) \[Category-A/Category-B/Category-B'/Category-C/Category-C'/Category-D/Category-E/Category-E']:** Select the appropriate fatigue detail category per AASHTO Table 6.6.1.2.3-1. The detail category determines the fatigue threshold and resistance for the connection details being checked. **ADTT:** The annual daily truck traffic is a parameter used in fatigue checks. **Number of Lanes Available to Trucks:** Number of lanes available to trucks. Used together with ADTT to derive the single-lane ADTT (ADTTSL) per AASHTO Table 3.6.1.4.2-1 for the fatigue resistance check. ## Ductility Parameter **Including the haunch in determining Dt \[Yes/No]:** This parameter can be used to specify whether the haunch will be included in ductility checks within the code checks. Since including the haunch is optional, the total depth is calculated based on the actual haunch depth if this parameter is set to 'Yes', or calculated conservatively if set to 'No'. {% hint style="info" %} The ductility-related code check can be performed either by making a conservative calculation or by directly using the modeled haunch depth. The screenshot below provides an example of excluding the haunch in determining Dt, with the parameter set to 'No' ![image-20241104-075915.png](https://openbrim.atlassian.net/wiki/download/attachments/2125496451/image-20241104-075915.png?api=v2) {% endhint %} ## Appendix A6 These provisions shall apply only to sections in straight bridges whose supports are normal or skewed not more than 20 degrees from normal. **Use Appendix A6 Provisions? \[Yes/No]:** The optional provisions of Appendix A6 account for the ability of compact and noncompact web I-sections to develop flexural resistances significantly greater than My. The potential benefits of the Appendix A6 provisions tend to be small for I-sections with webs that approach the noncompact web slenderness limit of AASHTO Eq. A6.1-1. If the user selects "Yes" for Appendix A6 provisions, the code check component will internally verify for additional requirements and will not use it if all conditions are not met. ## Appendix B6 This Article shall apply for the calculation of redistribution moments from the interior-pier sections of continuous span I-section flexural members at the service and/or strength limit states. These provisions shall apply only for I-section members that satisfy the requirements of Article B6.2.These optional provisions provide a simple rational approach for calculating the moment redistribution from interior-pier sections due to the effects of yielding. This approach utilizes elastic moment envelopes and does not require the direct use of any inelastic analysis methods. The restrictions of Article B6.2 ensure significant ductility and robustness at the interior-pier sections. **Use Appendix B6 Provisions? \[Yes/No]:** If the user selects "Yes" for Appendix B6 provisions, the code check component will internally verify for additional requirements and will not use it if all conditions are not met. If all conditions are met for the support stations, the code check will report the amount of major axis bending moment to be redistributed (Delta Mrd) from piers to span regions for strength and service limit states. This information can be used to determine if using Appendix B6 satisfies the AASHTO requirements for the support locations in their first run. **Mrd at Supports List (Strength) :** In the second run, the user needs to enter the Mrd values of each pier reported in the summary as an input to the code check for any span region adjacent to pier locations. This will help determine if the distributed moment can cause any problems at those locations. If the user wishes to utilize Appendix B6, they must define a separate template for each girder to correctly input the Mrd values at pier locations. **Mrd at Supports List (Service):** In the second run, the user needs to enter the Mrd values of each pier reported in the summary as an input to the code check for any span region adjacent to pier locations. This will help determine if the distributed moment can cause any problems at those locations. If the user wishes to utilize Appendix B6, they must define a separate template for each girder to correctly input the Mrd values at pier locations. {% hint style="info" %} Note that a moment value must be entered at all bearing points, even if it is zero. However, no moment should be assigned to support lines that are additionally placed solely for geometric adequacy. ![image-20250515-064738.png](https://openbrim.atlassian.net/wiki/download/attachments/2125496451/image-20250515-064738.png?api=v2) {% endhint %} **Adj. to Interior-Pier Section Stations (Str):** The user can specify the range for moment redistribution with station values along the PGL for each pier. To help users understand the behavior, the following logic can be applied: the demand will be redistributed, increasing the demand at the adjacent stations while decreasing the demand at the pier. The expected outcome is that the maximum demand value at the pier will decrease, and the maximum demand value at the adjacent stations will increase. However, the above logic is simply explained to demonstrate the behavior. For a more detailed explanation, users need to refer to the AASHTO code and OpenBrIM detailed report. **Adj. to Interior-Pier Section Stations (Srv):** The user can specify the range for moment redistribution with station values along the PGL for each pier. To help users understand the behavior, the following logic can be applied: the demand will be redistributed, increasing the demand at the adjacent stations while decreasing the demand at the pier. The expected outcome is that the maximum demand value at the pier will decrease, and the maximum demand value at the adjacent stations will increase. However, the above logic is simply explained to demonstrate the behavior. For a more detailed explanation, users need to refer to the AASHTO code and OpenBrIM detailed report. ## Deflection As specified in AASHTO 2.5.2.6.2, "The live load portion of Load Combination Service I of Table 3.4.1-1 should be used." Additionally, you can directly set a deflection case. **Criteria for Deflection L/:** The value to be used in the deflection limit calculation as specified in AASHTO 2.5.2.6.2. **Deflection Result Case from \[Service\_I-LL\_Case/User\_Input]:** Selection of the deflection case source. **Deflection Result Case:** Set Manual deflection case instead of Service 1 LL case. --- # Agent Instructions: 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: ``` GET https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/templates-for-code-check-and-load-rating-sig/steel-i-girder-code-check-t-sig.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.