> 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/concrete-u-girder-bridge-workflow/organization-cug/cross-project-data-cug/shared-substructure-cug.md).

# Shared Substructure \[CUG]

For a group of substructures bounded by a support line, objects can be chosen as a whole rather than selected individually by using the library object ‘Shared Objects’. All objects associated with that support line will be selected for sharing.

**Support Lines:**

Specify a support line or support lines, which will result in selecting the related elements to be shared. The objects that will be automatically selected are:

* Alignment,
* Bridge,
* Insertion Points,
* and All substructures below.

**Transfer Result Extractions \[YES/NO]:** The result extractions can be transferred if this parameter is set to ‘YES’. The results to be extracted must be defined in the **Analysis Results** section of **Cross-Project Data**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/organization-cug/cross-project-data-cug/shared-substructure-cug.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.