> 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/construction-stg/superstructure-construction-stg/girder-cross-frame-erection-complete-stg.md).

# Girder/Cross Frame Erection (Complete) \[STG]

Generally, girders and cross frames are constructed in a single stage. If partial girder and cross-frame erection is required, it is recommended to avoid using this component and instead navigate to "Girder Erection (Partial)" in the tree view.

## Girder Construction

**Stage:** During this stage, finite elements for girders and cross frames will be constructed and their self-weight will be applied concurrently.

**Bridge:** All girder and cross frame components of the selected bridge will be constructed at selected stage.

**Splice Load \[Ignore/Include]:** If splice weight loads are to be included in the FEA, set the option to 'Include' for this parameter. If the option 'Ignore' is selected, the weight loads of the splices will be neglected.

**Stiffener/Gusset Plate Load \[Ignore/Include]:** If the weight loads of the stiffeners or gusset plates are to be included in the FEA, select 'Include' for this parameter. If you need to neglect the weight loads of the stiffeners or gusset plates, select 'Ignore'.

**Girder Self Weight Factor:** The Girder Self-Weight Factor is a parameter used to adjust the contribution of a girder's own weight to the overall structural load calculations. This factor allows for the scaling or modification of the girder's self-weight in finite element analysis (FEA).


---

# 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/construction-stg/superstructure-construction-stg/girder-cross-frame-erection-complete-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.