> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/designer-guide/create-a-part.md).

# Create a part

Once a design part is approved, its designer creates the manufacturing part. That generates the routing and the MO, and the part appears on the shop floor.

![Design to manufacturing handoff](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-c342b4d752a28c299e24c21e767e53091699c41a%2F03-handoff.png?alt=media)

## Create one part

1. Open **Manufacturing › Parts**. Approved design parts are listed under **Approved for manufacturing** (you see your own; admins see all).
2. Click **Create part**. New Part opens, pre-filled from the design part. "Links to" confirms which design part it's linked to.

![New part opened from Create part, pre-filled and linked to 26-01102 Right rail](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-f9c0f20f68d00d86bd780dc5d69a25f47f86a1e9%2Fnew-part.jpg?alt=media) 3. Confirm the type (tube, sheet, shaft or print), material, color, dimensions and options. Attach the STEP file if you have one. 4. Save.

When you save:

* the part is linked to its design part, which becomes **in manufacturing**,
* the routing is generated from the type and options, and
* an MO (`MO-YY-####`) is created and appears in the first station's queue.

{% hint style="info" %}
You need the **Manufacturer** role to open the Manufacturing environment.
{% endhint %}

## Options set the route

| Option           | Effect                                                                       |
| ---------------- | ---------------------------------------------------------------------------- |
| Requires CNC     | Tube adds CNC Router after Bandsaw                                           |
| Has Bends        | Sheet adds Bend after Debur. Attach the bend drawing                         |
| Requires Lathing | Shaft uses Manual Lathe instead of Bandsaw. Attach a lathe drawing if needed |
| Color: bare      | Skips Coating. Prints never get Coating                                      |

See [Routing](/raidparts/reference/routing.md) for every route.

## Create many parts at once

1. Drop several STEP files on the **Parts** tab. They open in the Pending queue, with dimensions and a thumbnail read from each file.
2. Select rows and use **Apply to N selected** to fill shared fields, like material.
3. Click **Create part & MO** on a row, or **Create all complete** to create every finished row.

The same rules apply as for a single part; for example, bent sheet still needs a bend drawing.

Next: [Change or retire a part](/raidparts/designer-guide/change-a-part.md).


---

# 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.raidrobotics.org/raidparts/designer-guide/create-a-part.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.