> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/vex-cad/making-a-chassis/inventor-chassis/assemblies.md).

# Assemblies

In this page, we'll be going over how to create a new assembly.

Assemblies are files with the extension `.iam`. They let the user assemble multiple parts into a robot. When creating anything with more then one part, we will use an assembly to put the parts together.

## Creating a New Assembly

Once Inventor is open, click `File` in the top left corner, `New`, then `Assembly`.

![Inventor's File Menu](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7yGVyBrcpSR8SDSikj%2F-MfExsTMauY7LKqYC_Iy%2F-MfF1sVtmMh7tkHvl38N%2F1.png?alt=media\&token=8ff71d61-19ef-4d5a-8559-6b5f9b0a5307)

The first thing we do when creating any new file is to **save it** with `ctrl+s`. A window will pop up, name the assembly the name of the robot. Navigate to the robot folder you created in the previous article, click `Save` to save the new assembly.

![Save Pop-Up Window](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7yGVyBrcpSR8SDSikj%2F-MfExsTMauY7LKqYC_Iy%2F-MfF1sW63CMXkcAXucXt%2F2.png?alt=media\&token=0596ed8a-d0cc-476e-8903-92b93428668c)

When done, if we look in our robot folder, this is what you should see:\\

![Completed New Assembly](https://3510336827-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7yGVyBrcpSR8SDSikj%2F-MfExsTMauY7LKqYC_Iy%2F-MfF1sW9ttzAasG37sPd%2F3.png?alt=media\&token=0071e2cc-7c97-42de-b601-5d0a6e982f35)

## Contributors to this Article:

* Jess - EZ


---

# 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://wiki.purduesigbots.com/vex-cad/making-a-chassis/inventor-chassis/assemblies.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.