> 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/access-hole-design-sig/access-hole-load-sig.md).

# Access Hole Load \[SIG]

The Access Hole Load workflow item defines the edge loads applied to a previously defined Access Hole Model. Forces and moments can be specified independently for each of the four plate edges (left, right, top, bottom) and are converted internally into surface loads on the corresponding edge FE groups.

## General

**Plate:** Pick the Access Hole Model on which the edge loads are applied. The plate's length and width are read from the picked model to convert the edge forces into surface loads. Required; exactly one plate must be selected.

## Left Edge Load

Forces and moments applied uniformly across the left-edge strip of the plate (edge at `X = -Plate Length / 2`). Forces use `Force` units and moments use `Moment` units.

**Fx:** Total force along the X axis applied to the left edge.

**Fy:** Total force along the Y axis applied to the left edge.

**Fz:** Total force along the Z axis applied to the left edge.

**Mx:** Total moment about the X axis applied to the left edge.

**My:** Total moment about the Y axis applied to the left edge.

**Mz:** Total moment about the Z axis applied to the left edge.

## Right Edge Load

Forces and moments applied uniformly across the right-edge strip of the plate (edge at `X = +Plate Length / 2`).

**Fx:** Total force along the X axis applied to the right edge.

**Fy:** Total force along the Y axis applied to the right edge.

**Fz:** Total force along the Z axis applied to the right edge.

**Mx:** Total moment about the X axis applied to the right edge.

**My:** Total moment about the Y axis applied to the right edge.

**Mz:** Total moment about the Z axis applied to the right edge.

## Top Edge Load

Forces and moments applied uniformly across the top-edge strip of the plate (edge at `Y = +Plate Width / 2`).

**Fx:** Total force along the X axis applied to the top edge.

**Fy:** Total force along the Y axis applied to the top edge.

**Fz:** Total force along the Z axis applied to the top edge.

**Mx:** Total moment about the X axis applied to the top edge.

**My:** Total moment about the Y axis applied to the top edge.

**Mz:** Total moment about the Z axis applied to the top edge.

## Bottom Edge Load

Forces and moments applied uniformly across the bottom-edge strip of the plate (edge at `Y = -Plate Width / 2`).

**Fx:** Total force along the X axis applied to the bottom edge.

**Fy:** Total force along the Y axis applied to the bottom edge.

**Fz:** Total force along the Z axis applied to the bottom edge.

**Mx:** Total moment about the X axis applied to the bottom edge.

**My:** Total moment about the Y axis applied to the bottom edge.

**Mz:** Total moment about the Z axis applied to the bottom edge.


---

# 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/access-hole-design-sig/access-hole-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.