> 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/templates/spliced-i-girder-bridge-workflow/external-references-spig/project-3d-spig.md).
# Project 3D \[SPIG]
Use this section to consolidate the 3D models of one or more source projects into the current workflow — without pulling in their FEM data. This is the primary path for building **federated models**. Once a source project is linked, all of its objects appear in the 3D view, and any reports exposed for sharing (e.g. load-rating reports) are transferred alongside the geometry.
{% hint style="info" %}
For reports to travel with the 3D model, the source (master / global) project must declare them under **Organization → Cross-Project Data → Shared Objects**. Without that declaration, only geometry is imported.
{% endhint %}
## How to link a project
1. **Create a new all-in-one project.** Open **All-in-One Bridge Workflows → New Project**, name it, and enter the project.
2. **Open External References.** Click **Data** to show the spreadsheet, then use the gear icon on the left panel to pick **External References** from the workflow list.
3. **Add the source project.** In the tree, select **Project 3D**. On the row's cell-action menu (three dots) choose **Add Projects…**, pick the global/parent project, and click **Add**.
4. **Verify the metadata.** Once linked, the **Project ID**, **Project Name**, **Last Project Modification**, and **Last Project Sync** columns populate automatically.
5. **Trigger the initial sync.** From the **Name** cell's three-dot menu, choose **Sync Project**. This pulls the source model into the current project.
6. **View the imported model.** Click **Zoom Extents** to frame the new geometry in the 3D view.
## Parameters
**Name:** User-editable label for this project reference. Pick from the dropdown when first linking; rename at any time.
**Project ID:** Immutable identifier of the linked source project.
**Project Name:** Display name of the linked project. Updates automatically if the source is renamed. (Read-only)
**Last Project Modification:** Timestamp of the most recent change in the source project. Compare with **Last Project Sync** to decide whether a fresh sync is needed. (Read-only)
**Last Project Sync:** Timestamp of the most recent sync into this workflow. Re-run **Sync Project** if the source has changed since. (Read-only)
---
# 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/templates/spliced-i-girder-bridge-workflow/external-references-spig/project-3d-spig.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.