> 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/quick-guides/prestressed-i-girder-bridge-design-reports.md).

# Prestressed I Girder Bridge Design Reports

## Access the Precast I-Girder Training Example

{% hint style="info" %}
Follow the steps below to open the **Precast I-Girder Training Example**.
{% endhint %}

1. Sign in. The **Projects** screen opens. Click **New Project**, or **NEW** in the bar on the left. (With a project already open, click the **New** icon, the page icon next to the project name in the top bar.)

   ![Projects screen](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-8259d4ccd9f7506d86ed3e7c28047ffe210635e4%2Fprojects-screen-new-project.png?alt=media)
2. The **Project Templates** screen opens. Open the **Example Projects** folder.

   ![Project Templates screen](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-14402564cc1f44ace73ad72b5a381386b6981265%2Fproject-templates-screen.png?alt=media)
3. The folder holds two precast I-girder examples, **Precast I-Girder Training Example (Superstructure)** and **Precast I-Girder Training Example (Substructure)**. Click **New Project** on the one you want.

   ![Example Projects templates](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-5197810469b49df0f53f1ea1adedae010a03394b%2Ftemplates-example-projects.png?alt=media)
4. In the **Create Project** dialog, enter a name for your project, choose a **Folder** if you want one, and click **Create**. The project opens in the 3D view.

   ![Create Project dialog](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-927d95853809887c9990c739d337476a268205ee%2Fcreate-project-dialog.png?alt=media)

![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-112930.png?api=v2)

{% hint style="warning" %}
The initial download of the library components **takes approximately 2 minutes 30 seconds**. Subsequent openings of the same project are noticeably faster because OpenBrIM library objects are cached in your browser; loading then **takes less than 2–3 seconds**.
{% endhint %}

## View Design Reports of the Precast I-Girder Training Example

{% hint style="info" %}
Follow the steps below to run the precast I-girder code-check reports.
{% endhint %}

The Precast I-Girder Workflow supports the following code-check reports:

* Prestressed I-Girder Code Check
* Pier Cap Code Check
* Pier Column Code Check
* Pier Footing Code Check
* Pile Capacity Code Check

1. Make sure **FEM** in the middle of the top bar (**3D** | **FEM** | **Detailing**) is on — the **Analyze** button only appears when **FEM** is on.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-120315.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>The <strong>Analyze</strong> button typically <strong>takes around 20–25 seconds</strong> to appear.</p></div>
2. When the **Analyze** button appears in the top-left, the FE model has been compiled and is ready to run.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-115919.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-120457.png?api=v2)
3. Click **Analyze** to run the finite element analysis of the precast I-girder bridge.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-120357.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Analysis for this project typically <strong>takes around 2 minutes 20 seconds</strong> to complete.</p></div>
4. When the analysis finishes, click **Close** to exit the analysis interface.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-120848.png?api=v2)
5. Click **Design** to compute the parametric design parameters and collect the analysis results needed for the reports.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-120952.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>The design run for this project generally <strong>takes approximately 7 minutes 20 seconds</strong> to complete.</p></div>
6. When the design run finishes, click **OK** to start viewing the reports.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-121845.png?api=v2)
7. Click **Report** and **Detailed Report** in succession to display the available reports.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230711-122203.png?api=v2)
8. **Detailed Report** opens the full set of design outputs.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533591/image-20230706-105121.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/quick-guides/prestressed-i-girder-bridge-design-reports.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.
