> 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/parametric-bridge-engineering.md).

# Parametric Bridge Engineering

## Access an Example Steel Bridge Model

{% hint style="info" %}
Follow the steps below to open the **Steel 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. Click **New Project** on the **Steel I-Girder Training Example** card.

   ![Steel I-Girder Training Example card](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-1cfcafab90187e24638a8bdd36bcfde8f0aeaf71%2Fexample-projects-steel-i-girder-card.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)

{% 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 %}

![Steel I-Girder Training Example in the 3D view](https://2645910244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGR3Y2oTOZjlXFJKoQ7ar%2Fuploads%2Fgit-blob-161590db90b30d71e39a93d85b27a3d566db872f%2Fsteel-i-girder-training-example-opened.png?alt=media)

***

## OpenBrIM Parametric Modeling

This section demonstrates how OpenBrIM's cloud-based parametric approach updates every connected output (3D model, FEA model, drawings, reports) when you change a single input.

{% hint style="info" %}
In the steps below, you will modify the **Web Depth** parameter of a girder in the spreadsheet. Both the 3D model and the FEA model will update automatically.
{% endhint %}

1. Click **Sheet** at the right of the 3D view's toolbar to open the spreadsheet.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-082508.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-083136.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><ul><li>To resize the spreadsheet, drag the divider between it and the 3D view.</li><li>To close the spreadsheet, click <strong>Sheet</strong> again.</li></ul></div>
2. Click **Plate Girder** under **Superstructure** in the workflow tree. *All project girders and their parameters appear in the spreadsheet.*

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-083410.png?api=v2)
3. To compare the FE model before and after the change, click **FEA** in the left bar to switch to the Finite Element view. The left bar also has **3D**, **2D**, **DOCS.**, **SITE**, **USERS**, **REVISIONS**, **SOURCE** and **HELP**.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-082055.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-082436.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20231025-193909.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Zoom with the mouse scroll wheel. Pan by holding the scroll wheel down while moving the mouse. To recenter the view, click the <strong>Zoom Extents</strong> button in the top-right corner; after selecting an object, <strong>Zoom Extents</strong> orbits the view around that object. Rotate by dragging with the left mouse button.</p></div>

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/Screenshare%20-%202023-07-13%2010_59_28%20AM-20230713-080117.gif?api=v2)
4. The current Finite Element model uses an 84 in web depth. To change it for girder **G4**, click the **Web Depth** cell for that girder and enter **55** inches.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-082823.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-083033.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>After the change, the 3D model and Finite Element model take roughly 10 seconds to refresh. OpenBrIM recompiles using your inputs to regenerate the 3D model, FEA model, CAD drawings, and dynamic reports (such as the quantity report) so all outputs stay in sync.</p></div>
5. The new Finite Element model now reflects the updated web depth.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-083348.png?api=v2)
6. Click **3D** in the left bar to switch back to the 3D view.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-083959.png?api=v2)
7. The change is visible in both the 3D and Finite Element views.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230713-084708.png?api=v2)

{% hint style="info" %}
For a full description of girder plate dimensions, see [Plate Girder \[SIG\]](https://docs.openbrim.org/templates/steel-i-girder-bridge-workflow/superstructure-sig/steel-girders-sig/plate-girder-sig.md).

For a worked example, see [Plate Girder \[EX1-SIG\]](https://docs.openbrim.org/examples/steel-bridge-examples/example-steel-i-girder-bridge-ex1-sig/superstructure-ex1-sig/steel-girders-ex1-sig/plate-girder-ex1-sig).
{% endhint %}

***

## OpenBrIM Spreadsheets: Excel-Like Functionality with Parametric Dependencies

This section shows how OpenBrIM spreadsheets behave like Excel — cells can reference one another to keep related parameters in sync.

{% hint style="info" %}
Cross-frame skew, roadway skew, and support-line skew are independent inputs by default, so the same value must be entered in three places. The steps below link them so that changing the support-line skew updates the others automatically.
{% endhint %}

1. Click **Support Line** under **Bridge Geometry** in the workflow to access the skew angle parameter.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-095956.png?api=v2)
2. To change the skew angle of **Abut1**, click the corresponding cell (marked in red).

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-112143.png?api=v2)
3. With the skew angle of **Abut1** set to 0, the bridge appears as shown.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-102036.png?api=v2)
4. With the skew angle of **Abut1** set to **−15°**, the bridge appears as shown.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-103455.png?api=v2)

{% hint style="info" %}
The cross-frames are no longer aligned with the support line.

To link them parametrically:

1. Copy the support line's skew angle value with **Copy Reference**.

2. Paste the parametric expression into the cross-frame's skew angle.

3. The cross-frame skew now follows the support line skew automatically.
   {% endhint %}

4. Click the skew angle cell for **Abut1**. Click the three-dot menu that appears on the right side of the cell, then choose **Copy Reference**. The skew angle parameter (not the value) is copied.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-105048.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>The parameter copied: <code>=Abut1.s_skew</code></p></div>

5. Expand **Cross Frames** under **Superstructure** in the workflow, then click **Cross-frame K Top** to access its parameters.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-104914.png?api=v2)

6. Click the skew angle cell for **CFTK1**. Open the three-dot menu that appears on the right side of the cell and choose **Paste**.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-110050.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can also paste the copied parameter into the active cell with <code>CTRL+V</code>.</p></div>

7. Repeat the paste for **CFKT28** and **CFKT29**. *The cross-frames are now aligned with the support line.*

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-110452.png?api=v2)

8. Cross-frame skew angles are now parametrically linked to the support-line skew, so changing one updates the others.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230712-084553.png?api=v2)

{% hint style="success" %}
The cross-frame skew now references the support line's skew the way one Excel cell references another. OpenBrIM cells accept arithmetic, functions, and logical operators, so more complex equations are supported. See [Mathematical Functions](https://docs.openbrim.org/developers/paramml-developer-guide/functions/mathematical-functions) in the ParamML documentation.
{% endhint %}

### Typing an equation in a cell

Any number cell takes an equation instead of a value. Type it directly into the cell, with or without a leading `=`:

* Refer to another object's parameter as `ObjectName.parameter`, for example `Abut1.s_skew` or `Abut1.s_skew / 2`. **Copy Reference** writes this text for you.
* Use arithmetic (`+`, `-`, `*`, `/`, `^`), comparisons, and functions such as `max()`, `round()` and `iif()`.

While you type, the value of the equation and the parameters it uses appear under the cell. Later, rest the pointer on a cell that holds an equation to see the same note. With several rows of one column selected, the note also tells you which key writes the equation to all of them.

***

### Aligning Roadway with Skew Angle

{% hint style="info" %}
Use the same Copy Reference approach to align the roadway with the skew angle of the support line.
{% endhint %}

1. Expand **Superstructure Attachments** in the workflow and click **Roadway** to access the roadway alignment parameters.
2. Open the three-dot menu on the right of the **Roadway Dimensions** cell and click **Open Table...**.
3. Paste the skew angle copied from **Abut1** into the **Skew** parameter at station 0.

![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-111028.png?api=v2)

![](https://openbrim.atlassian.net/wiki/download/attachments/2231271425/image-20230705-111816.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/parametric-bridge-engineering.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.
