> 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/precast-i-girder-bridge-workflow/organization-pig/cross-project-data-pig.md).

# Cross-Project Data \[PIG]

For objects from a Global/Master model to be transferred to a Child/Local model, **Cross-Project Data** objects can be utilized. The necessary definitions for sharing bridge elements, design reports, and/or analysis results from a model must be specified in this section. Guidance on transferring the objects to another project can be found on the [External References](/templates/precast-i-girder-bridge-workflow/external-references-pig.md) .

The use of such objects may be beneficial when:

* Several engineers are working on different elements of the same bridge. Each engineer can work on a separate element, making the necessary improvements without affecting the main project. After finalizing a design, the master project can be updated accordingly.
* Global models might require a few adjustments. By sharing multiple bridge elements and objects (code checks, etc.) from the Global Model, Local Models can be created and used efficiently .

For further explanation on how to share **bridge elements and objects**—such as an object that exists in one project (e.g., for code checks) with another project—while keeping the main project intact and iterating on related objects to enhance the design, refer to the following pages.


---

# 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/precast-i-girder-bridge-workflow/organization-pig/cross-project-data-pig.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.