> 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/wind-load-sig/wind-load-on-live-load-sig/wl-custom-sig.md).

# WL Custom \[SIG]

The following explanation elucidates the utilization of a custom wind on live load object for defining loads as per the 9th Edition of AASHTO. Users can then tailor it to their specific requirements. If customization is unnecessary, users can directly employ the Wind on Live Load AASHTO object to define their loads. In this case, the library object will automatically generate all the related loading conditions.

Per AASHTO 9th Edition, wind load on live load shall be represented by an interruptible, moving force of 0.10 klf acting transverse to, and 6.0 ft above, the roadway and shall be transmitted to the structure. For various angles of wind direction, the transverse and longitudinal components of the wind load on live load may be taken as specified in Table 3.8.1.3-1, with the skew angle measured from the perpendicular to the longitudinal axis of the bridge in plan

![](https://openbrim.atlassian.net/wiki/download/attachments/2125365283/image-20230317-205549.png?api=v2)

For each design lane centerline location, the user needs to generate load cases for each of the nine angles of attack (-60, -45, -30, -15, 0, 15, 30, 45, and 60) computed for both the right-to-left and left-to-right wind directions, resulting in a total of 18 cases.

## General

**Line:** Select the lane position defined in the previous step.

**Stage:** Choose the stage at which to apply the wind load.

**Transverse Force:** Enter the transverse component values here as per AASHTO Table 3.8.1.3-1.

**Longitudinal Force:** Enter the longitudinal component values here as per AASHTO Table 3.8.1.3-1.

**Moment Due to Transverse Force:** As mentioned in AASHTO, the moving force is applied 6.0 feet above. Therefore, the transverse force value should be multiplied by 6 feet and entered here.

**Moment Due to Longitudinal Force:** As mentioned in AASHTO, the moving force is applied 6.0 feet above. Therefore, the longitudinal force value should be multiplied by 6 feet and entered here.

![](https://openbrim.atlassian.net/wiki/download/attachments/2125365283/image-20230816-114120.png?api=v2)


---

# 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/wind-load-sig/wind-load-on-live-load-sig/wl-custom-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.