> 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/external-references-pig/project-analysis-results-pig.md).

# Project Analysis Results \[PIG]

Use this section to import analysis results computed in another project into the current workflow. The source project must expose the results under **Organization → Cross-Project Data → Analysis Results**; this page is the consumer side of that link.

Analysis results are always tied to the object they act on (a girder, column, pile, etc.), so the object itself must first be shared via **Project Objects** before its results appear here. With a valid setup in the source project — and the **Transfer Result Extractions** flag set to **YES** — the result rows populate automatically as linked objects are synced.

![image-20241213-142355.png](https://openbrim.atlassian.net/wiki/download/attachments/2803204097/image-20241213-142355.png?api=v2)

![image-20241213-142445.png](https://openbrim.atlassian.net/wiki/download/attachments/2803204097/image-20241213-142445.png?api=v2)

![image-20241213-142134.png](https://openbrim.atlassian.net/wiki/download/attachments/2803204097/image-20241213-142134.png?api=v2)

## Extraction Settings

**Project:** Source project from which the analysis result is imported. Pick from the projects already linked under **External References**.

**Object:** Object within the source project whose result is extracted (e.g. a girder, column, or pile). The pick list is filtered to objects the source project has exposed for sharing.

**Result Extraction Method:** Method used to pull the result from the source project (e.g. cumulative or incremental staged-construction result, envelope, or combination). Matches the method configured on the source project's Analysis Results definition.

**Force Settings:** Summary of the Maximize-Force and Min/Max options used at the source to identify the critical result.

## Extracted Forces

**Fx:** Extracted axial force from the source project. (Read-only)

**Fy:** Extracted transverse shear force. (Read-only)

**Mx:** Extracted moment about X. (Read-only)

**My:** Extracted moment about Y. (Read-only)

**Mz:** Extracted moment about Z. (Read-only)

**Coordinate System:** Coordinate system in which the forces and moments above are reported (local or global). (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/precast-i-girder-bridge-workflow/external-references-pig/project-analysis-results-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.