> 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/creating-a-local-substructure-model-for-soil-structure-interaction-from-a-global-model.md).

# Creating a Local Substructure Model for Soil-Structure Interaction from a Global Model

Once your global model is ready, you can use the workflow below to:

1. **Run a nonlinear analysis on the substructure** — useful for analyzing or checking slender columns independently.
2. **Run a soil-structure interaction (SSI) analysis** — incorporate nonlinear springs to evaluate the interaction between the soil and the structure.

The main benefit is that any change to the global model — or any modification that affects analysis results — can be pushed to the local model with a single sync. Change management stays simple.

## Prepare the Global Model for Substructure and Result Transfer

1. Prepare the global model for transfer. Navigate to **Organization > Cross-Project Data > Shared Substructure**. Select the **Support Line** and set **Transfer Result Extractions** to **Yes**.

   For the selected support lines, Shared Substructure shares the bridge and its alignment, the pier caps and bents, the pier columns and their bracing, the footings, the piles and pile layouts with their soil sets and soil layers, the insertion points and bearings, and the sections, materials and reinforcement these objects use. The local model therefore receives this geometry; you do not model it again. With **Transfer Result Extractions** set to **Yes**, the bundle also carries every result extraction defined under **Analysis Results** in the global model (all its Bearing Forces and Column Forces rows, not only those of the selected support lines).

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-213736.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-213906.png?api=v2)
2. Navigate to **Organization > Cross-Project Data > Analysis Results > Bearing Forces** and select all bearings of the substructure together with the result cases used for force extraction. (See [Bearing Forces](https://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/organization-stg/cross-project-data-stg/analysis-results-stg/bearing-forces-stg.md) for details.) Configure the extraction settings to match your use case.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215245.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215307.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215459.png?api=v2)
3. Open the **Extracted Forces** tab, select the Bearing Forces rows, open the three-dot menu of one of their cells and choose **Extract Result**. The forces appear in the spreadsheet and **Last Result Extraction** shows the date. The global model is now ready to transfer the substructure model and its results.

   The local model receives the forces as they were at the last extraction. After the global analysis changes, run **Extract Result** again before syncing the local model.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215635.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215743.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-215834.png?api=v2)

## Set Up the Local Substructure Model from the Global Model

1. Create a new project from the workflow template that matches the bridge, for example **Steel Bridge Workflows → Steel I Girder Bridge Workflow → New Project**. Enter a name for the new project.
2. Click **Data** to open the spreadsheet and select **External References** in the workflow tree on the left. If the tree has none, open the workflow menu (the ▾ next to the workflow name above the tree), choose **Import new workflow…** and pick **External References**.
3. In the tree view, click **Project Objects**. Open the spreadsheet's ⋮ menu in the **top-left corner** of the sheet (above the row numbers) and choose **Add Projects…**. Select your global / parent project in the dialog and click **Add**. A new row appears with the project's **Project ID** filled in.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241128-125206.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241128-125507.png?api=v2)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Add Projects…</strong> acts on the whole sheet, so it is on the corner ⋮ menu and not on a cell's menu. The menu of the empty <strong>(New)</strong> row offers only <strong>Paste</strong>. Typing a name into the <strong>Name</strong> cell creates a row that is not linked to any project (its <strong>Project ID</strong> stays empty), and that row cannot be synced. Delete such a row and add the project with <strong>Add Projects…</strong> instead.</p></div>
4. On the new row, open the menu of the **Shared Objects of External Project** cell (the ⋮ button on the cell, or right-click it) and choose **Choose Shared Objects…**. Select the shared substructure the global model publishes and click **Add**.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241128-125617.png?api=v2)
5. Open the row's menu again (the ⋮ button, or right-click any of its cells) and choose **Sync Shared Object…** to complete the import.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Pull Shared Data…</strong> on the same menu does steps 4 and 5 in one click when the global model publishes exactly one shared object set. When it publishes more than one, choose the set with <strong>Choose Shared Objects…</strong> first.</p></div>
6. Click **Zoom Extent** ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-205754.png?api=v2) to view the substructure. In the tree view, synced objects are shown in **green** instead of the default **blue**. In the spreadsheet, each synced object's name cell shows an attachment icon at the bottom-right. Each subsequent sync overwrites the local data for these objects with whatever the global model contains.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-205852.png?api=v2)
7. To protect specific objects from being overwritten — for example, when you are designing the pier cap or pier column and don't want their data changed by the next sync — open the three-dot menu next to the object and choose **Disable Sync**.

   Sync-disabled objects show:

   * A **purple** color in the tree view.
   * An **unlock icon** instead of the attachment icon in the spreadsheet cell.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-210430.png?api=v2)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-210506.png?api=v2)
8. With the substructure imported, add the additional objects needed for analysis. Create at least two construction stages:

   * **Stage 1** — construction of the substructure.
   * **Stage 2** — application of bearing loads.

   Then build the substructure inside Stage 1. (This guide assumes familiarity with creating stages and constructing substructure elements in OpenBrIM. If you need an introduction, see the **Steel I Girder Training Example**.)

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-210817.png?api=v2)
9. Set the **Nonlinear** property of the stages to **Yes** to enable nonlinear analysis.

   ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-224209.png?api=v2)
10. Define the bearing loads. To wire them to the analysis results extracted from the global model:

    1. Navigate to **External References > Project Analysis Results** in the tree view. Its rows arrived with the sync in step 5: one row per result extraction (Bearing Forces or Column Forces row) of the global model, with its **Project** and **Object** filled in and the forces read-only. Nothing is picked here.
    2. Select all the cells in the results table.
    3. Click **Copy Reference**.
    4. Paste the parameters into the bearing-load spreadsheet — an **f(x)** icon appears in the bottom-left of each cell.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-211558.png?api=v2)

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-212731.png?api=v2)

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-212916.png?api=v2)
11. Define the **Soil Set** and **Soil Layers** (this guide assumes familiarity with creating soil sets and layers). Then return to the **Pile Layout FEA** tab and set **Soil Spring Type** to **Nonlinear Spring from the Soil Set**.

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-213233.png?api=v2)

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-212339.png?api=v2)

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-213302.png?api=v2)

    ![](https://openbrim.atlassian.net/wiki/download/attachments/2803269633/image-20241127-213314.png?api=v2)

{% hint style="warning" %}
Loads transferred from the superstructure may already include factors — for example, the Strength I combination typically applies a 1.25 factor to Dead Load. Those factors are **not** automatically applied to substructure self-weight in this local model, so you must apply the same factor to the substructure dead load yourself.

Wind loads applied directly to the substructure are also not transferred, because only forces at the bearing level are transferred. Define a separate wind-load case for the substructure if you need to account for it.
{% 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/quick-guides/creating-a-local-substructure-model-for-soil-structure-interaction-from-a-global-model.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.
