> 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/substructure-sig/pier-sig/steel-i-girder-bent-cap-sig/bearing-insertion-point-sig.md).

# Bearing Insertion Point \[SIG]

## **Bridge Parameters**

**Location:** This parameter specifies the location of the bearing insertion point. A previously created support line can be chosen for location definitions.

**Longitudinal Offset:** The longitudinal offset for the bearing insertion point can be specified to determine its location along the longitudinal direction.

**Transverse Offset:** The transverse offset for the bearing insertion point, with respect to the chosen support line, can be specified by this parameter. A value of "0" indicates that the bearing insertion point's center is located at the center of the chosen support line.

{% hint style="info" %}
The positive direction of the Y-axis will be to the left when looking upstream along the PGL. However, based on the requests of engineers who have been using OpenBrIM for their bridge projects, positive transverse offset values will indicate the right-hand side when looking upstream along the PGL. This distinction should be taken into account when defining the location of bridge elements using transverse offset values (where positive transverse offset indicates the right side), as well as when making definitions related to FEM and loading (where positive Fy indicates the left side along the PGL).
{% endhint %}


---

# 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-i-girder-bridge-workflow/substructure-sig/pier-sig/steel-i-girder-bent-cap-sig/bearing-insertion-point-sig.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.
