> 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/loading-sig/loads-sig/static-loads-sig/vehicle-load-sig.md).

# Vehicle Load \[SIG]

## General

**Bridge:** The bridge alignment the vehicle load is applied to. Typically set to the active Bridge Alignment.

**Stage:** Construction or service stage at which the vehicle load acts. Selected from the stages defined under Construction.

**Station:** Station along the PGL where the vehicle is placed. Enter a length value.

**Transverse Offset:** Transverse offset, perpendicular to the PGL, that defines the lateral position of the vehicle load. Positive values shift the load to the right when looking upstation.

**Vehicle:** Vehicles can either be imported or manually defined by the user under Influence Surface-Based Live Load/Braking Load/Centrifugal Load and assigned here. A typical default is the HL-93 design truck.

**Force (Gravity) (readonly):** The gross vehicle weight of the chosen vehicle is displayed to the user under this column. (Read-only)


---

# 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/loading-sig/loads-sig/static-loads-sig/vehicle-load-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.