> 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-tub-girder-bridge-workflow/superstructures-code-check-stg/access-hole-design-stg.md).

# Access Hole Design \[STG]

### Modeling and Analysis of Access Holes in Tub Girders

Access holes may be required depending on specific project needs. When incorporating access holes into the design and analysis of tub girders, the following considerations should be addressed:

1. **Localized Stress Concentrations**\
   Access holes introduce significant stress concentrations in localized areas. To accurately capture these effects, generate **Finite Element Models (FEM)** with a more refined mesh for the specific access hole regions.
2. **Simplified Global Models**\
   To maintain the simplicity and efficiency of the global model, create a separate model tailored specifically for the access hole using the **Steel Tub Girder Workflow**. This workflow accommodates the unique characteristics of access holes, allowing the refined analysis to focus on localized regions without complicating the overall global model.

This two-model approach ensures the global model remains efficient while the detailed model addresses the critical stress concentrations caused by access holes effectively.

For comprehensive instructions on using Access Hole objects, refer to the relevant section in the documentation.


---

# 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-tub-girder-bridge-workflow/superstructures-code-check-stg/access-hole-design-stg.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.
