> 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/interoperability.md).

# Interoperability

## Access the Steel I-Girder Training Example

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

![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)

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

## Interoperability

{% hint style="info" %}
The OpenBrIM platform can export 3D models, 2D drawings, and FEA models to various file formats and re-sync the exports whenever a parameter changes. The steps below walk through the export workflow.
{% endhint %}

1. Click **Sheet** at the right of the 3D view's toolbar to open the spreadsheet. In the **Girder Bridge** section in the lower-left, open the **Export** tree-view item.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162042.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162123.png?api=v2)
2. On the **Export File** tab, click the **Type** cell to choose the export type: i) Project Inputs, ii) 3D Model, iii) Finite Element Model, iv) 2D Drawings.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-161240.png?api=v2)
3. Choose the file format. The available formats update automatically based on the export type.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230711-075126.png?api=v2)
4. Set the destination folder for the export.

   1. Click the three-dot menu in any cell and choose **Set Project Directory on Local Disk** to specify the main folder on your machine.
   2. Click **Select Folder** and grant the permission requested by OpenBrIM.

   The path to the main folder varies per user, so it is saved in your browser cache rather than in the cloud. Pointing this at a ProjectWise folder lets exports re-sync automatically after each parameter change.

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

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-163019.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-163104.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-163141.png?api=v2)
5. Name each export file.

   1. In the **File Name** column, click the three-dot menu and choose **Set File Name on Local Disk**.
   2. Type a name (and any sub-folder structure) and click **Save**.

   The relative path is saved in the cloud — sub-folders are typically the same for every user, even when the main directory differs.

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

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-163543.png?api=v2)
6. The configured file name and partial path appear in the cells. The main directory is intentionally hidden so the same project can sync to different machines.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230711-075526.png?api=v2)
7. The final cell action in the three-dot menu is **Sync to Local Disk** — it writes (or rewrites) the export to disk using current parameters. Select multiple cells to sync several files at once.

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

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230710-164209.png?api=v2)
8. The exported files are now on your local disk.

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

## More on the Interoperability Features

{% hint style="info" %}
The videos below illustrate how OpenBrIM's cloud-based parametric approach keeps exports and downstream tools in sync.
{% endhint %}

**Change alignment and sync DGN files**

![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/MicroStationExport%20\(1\).mp4?api=v2)

**Change alignment, sync DGN files, and re-sync reference files in MicroStation**

![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/MicroStationReSync%20\(1\).mp4?api=v2)

{% hint style="info" %}
The remaining sub-sections cover the export options for the three engineering model types:

i) 3D Model ii) Finite Element Model iii) 2D Drawings
{% endhint %}

### Export 3D Model (.obj, .gltf, .ifc v4.3, .dxf, .dwg, .dgn)

1. Open the spreadsheet with **Sheet**. Set **Type** to **3D Model** and pick one of: .obj, .gltf, .ifc v4.3, .dxf, .dwg, .dgn.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162042.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162123.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20231025-185933.png?api=v2)
2. For 3D DGN export, the DGN settings let you choose between mesh and smart-solid output. Then [configure the file name and path as in step 4 above](#interoperability).

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

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

{% hint style="info" %}
When the project has active requirement sets (the owner's IDS files in Docs), every IFC export is checked against them before the file is saved. IFC files from other software can be checked against the same sets. See [Project Requirements (IDS)](https://docs.openbrim.org/quick-guides/interoperability/project-requirements-ids.md).
{% endhint %}

### Export 2D Drawings (.dgn, .dxf, .dwg)

1. Open the spreadsheet with **Sheet**. Set **Type** to **2D Drawings** and pick one of: .dxf, .dwg, .dgn. A .dwg is the .dxf saved as a DWG by AutoCAD in Autodesk's cloud, and each one counts toward the workspace's daily DWG exports.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162042.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162123.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20231025-190802.png?api=v2)
2. Projects often contain multiple 2D CAD drawings, so you must pick which to export. In the **Object** column, use the **Choose Drawing...** cell action. Then [configure the file name and path as in step 4 above](#interoperability).

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

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20231025-191145.png?api=v2)
3. The project must contain at least one CAD drawing. Add drawings via the library objects in the CAD section.

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

### Export FEA Model (.lar, .s2k, .b2k, .tcl, .mct)

1. Open the spreadsheet with **Sheet**. Set **Type** to **Finite Element Model** and pick one of: .lar, .s2k, .b2k, .tcl, .mct. The list also offers .xls, but on this Export object it exports the project inputs instead; to write the FE model and its analysis results to Excel, use **Export** in the project menu (see [Export from the Project Menu](#export-from-the-project-menu)).

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162042.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20230704-162123.png?api=v2)
2. OpenBrIM exports the full finite element model — including loads, not just nodes and shells — for CSI Bridge, LARSA 4D, and Midas Civil. If exported data is missing, contact OpenBrIM support. Then [configure the file name and path as in step 4 above](#interoperability).

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

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

### Import FEA Model (LARSA 4D .lar, SAP2000 .s2k, CSI Bridge .b2k, Midas Civil .mct)

1. Switch to the **FEA Workflow** to import finite element models from LARSA 4D, SAP2000, CSI Bridge, or Midas Civil.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2231533569/image-20231025-192227.png?api=v2)
2. Click **Import** and select a .lar, .s2k, .b2k, or .mct file.

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

## Import

Click the project name (top left), choose **Import…** and pick the file. Import reads only these formats:

| File                                                                                  | What it brings in                                                                                                                                                                             |
| ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **LandXML** (.xml)                                                                    | Alignments and terrain surfaces. Set the project's geographic coordinate system first: see [Import Alignment (.landxml)](https://docs.openbrim.org/quick-guides/import-alignment-landxml.md). |
| **DXF** (.dxf)                                                                        | Each file becomes a drawing in the project.                                                                                                                                                   |
| **LARSA 4D** (.lar), **SAP2000** (.s2k), **CSiBridge** (.b2k), **Midas Civil** (.mct) | A finite element model.                                                                                                                                                                       |
| **MDX** (.MDX)                                                                        | Read through an import specification from the library, which you choose when you import.                                                                                                      |
| **BIM structural package** or **Tekla** package (.json)                               | Structural elements from those packages.                                                                                                                                                      |
| **Revit** (.rvt)                                                                      | Converted by Autodesk first, then imported. Only in workspaces set up for the conversion.                                                                                                     |

You can pick several LandXML or DXF files at once; the other formats are imported one file at a time.

{% hint style="info" %}

* **No live link to other software.** Models move between OpenBrIM and other tools through the files on this page, for example IFC 4.3, DGN, DXF or DWG out, and LandXML in and out.
* **Exports are one-way.** The Project Inputs export is a spreadsheet to read; it cannot be imported back. To give another user the same model, share the project with them (see [Project Users](https://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/projects-users.md)); someone who can only view it can use **Copy to my account…** in the project menu.
* **Keeping a copy.** Exported files are outputs, not a project OpenBrIM can open again. The project itself stays in the cloud with its full revision history. For a separate copy, [duplicate the project](https://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/open-project.md#duplicating-a-project).
  {% endhint %}

### Export from the Project Menu

For a one-off file, click the project name, choose **Export…**, pick what to export and the format:

| Export                   | Formats                                                                                                       |
| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Project Inputs**       | Microsoft Excel (.xls)                                                                                        |
| **3D Model**             | .obj, IFC v4.3 (.ifc), AutoCAD DXF (.dxf), AutoCAD DWG (.dwg), MicroStation DGN (.dgn), Tekla JSON (.json)    |
| **2D Drawings**          | AutoCAD DXF (.dxf), AutoCAD DWG (.dwg), MicroStation DGN (.dgn)                                               |
| **Analytical Model**     | LARSA 4D (.lar), CSI Bridge (.b2k), Midas (.mct), CSI SAP2000 (.s2k), Microsoft Excel (.xls), OpenSees (.tcl) |
| **Alignments & Terrain** | LandXML 1.2 (.xml)                                                                                            |

The **Export** item in the workflow tree (above) writes most of these formats, and can re-sync the files to your disk whenever the model changes.


---

# 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/interoperability.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.
