> 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-sig/connections-sig.md).

# Connections \[SIG]

This section of the workflow is designed to create connection element definitions for 3D models, which are used for code checks and visualization purposes.

If the weight loads of these elements need to be applied to the bridge model, there are several parameters on the spreadsheet under **Construction → Superstructure Construction → Girder Erection (Partial) / Girder/Cross-Frame Erection (Complete)**. By setting the relevant parameters to 'Include' or 'Ignore,' the weight loads of the modeled connection elements can either be applied or excluded.

The parameters available for such definitions are:

On both spreadsheets, Girder/Cross-Frame Erection (Complete) and Girder Erection (Partial):

* Splice Load \[Include/Ignore],
* Stiffener/Gusset Plate Load \[Include/Ignore].

Currently, OpenBrIM enables users to model the following:


---

# 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/steel-i-girder-bridge-workflow/superstructure-sig/connections-sig.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.