> 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/analyze-and-design-ex1-stg.md).
# Analyze and Design
This section explains how to run structural analysis and design verification for the Steel Tub Girder Bridge.
{% hint style="info" %}
**Navigation:** Analyze and Design
{% endhint %}
## Overview
OpenBrIM computes parametric equations to create 3D/FEA/CAD representations based on project inputs. The process includes:
* **FEA Model Generation:** Node merging, meshing, load generation, influence surface coefficients
* **Analysis:** Time-dependent staged construction analysis
* **Design:** AASHTO code compliance verification with DC ratio calculations
{% hint style="info" %}
After parameter changes, you can rerun analysis or use previous results if the change doesn't affect the FEA model.
{% endhint %}
## Steps
### Step 1: Run Analysis
Click the **Analyze** icon and select **Run Analysis**.
Quick Tip: Using Previous Results
If you have already performed an analysis and wish to use the results in the design section, click **Use Previous Analysis Results**.
### Step 2: Run Design
Click the **Design** icon. OpenBrIM displays the estimated design process duration.
### Step 3: View Design Report
Click the **Report** icon and select **Design Report**.
### Step 4: Review Results
Switch between sections in the **Summary Report** tree view to review results.
## Verification
{% hint style="success" %}
After completing these steps, review the design report to verify AASHTO compliance for all components.
{% endhint %}
---
# 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/analyze-and-design-ex1-stg.md?ask=&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.