> 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/design/part-numbers-and-boms/part-numbers.md).

# Part numbers

{% hint style="info" %}
Copied from the [RAIDParts guide](https://docs.raidrobotics.org/raidparts/reference/part-numbers) and kept in sync automatically. Edit it in the RaidParts repo (`docs/`), not here.
{% endhint %}

Every part we make has an 8-character part number, like `26-01101`. RAIDParts assigns it when a designer adds the part to the BOM, and it never changes. A drawing, a CAM program, a label and the part on the shelf all carry the same number, so everyone knows exactly which part they have.

## How a part number is built

`YY-##A@@`

| Characters | Example | Meaning                                                            |
| ---------- | ------- | ------------------------------------------------------------------ |
| `YY`       | `26`    | Season year                                                        |
| `-`        | `-`     | Always a dash                                                      |
| `##`       | `01`    | Subsystem code, set for the season in **Admin › Subsystems**       |
| `A`        | `1`     | Subassembly number, 1 to 9, assigned in order within the subsystem |
| `@@`       | `01`    | Part number within the subassembly, 01 to 99                       |

Subsystem codes are set by admins and design leads; see [Seasons and the Library](https://docs.raidrobotics.org/raidparts/admin/seasons-and-library). Subassembly and part numbers are assigned by RAIDParts when you click **+ Assembly** and **+ Part**; see [Build the BOM](https://docs.raidrobotics.org/design/part-numbers-and-boms/build-the-bom.md).

## Examples

| Item                 | Number     | Why                                      |
| -------------------- | ---------- | ---------------------------------------- |
| Drivetrain subsystem | `26-01000` | Subsystem `01`, no subassembly or part   |
| Chassis subassembly  | `26-01100` | First subassembly in Drivetrain, no part |
| Left chassis rail    | `26-01101` | Part `01` in the Chassis subassembly     |
| Belly pan            | `26-01102` | Part `02` in the Chassis subassembly     |

RAIDParts shows numbers only for design parts. The subsystem and subassembly numbers above follow the same pattern with zeros and are used to name files in Fusion.

## Rules

1. **Get the number before you model.** Add the part in **Design › Bill of materials** first, then start it in Fusion.
2. **Lead with the number.** Every Fusion part and assembly name starts with its number, then a common name: `26-01101 Chassis Left Rail`.
3. **Never reuse a number.** A part that is no longer used is marked obsolete in RAIDParts and keeps its number. See [Change or retire a part](https://docs.raidrobotics.org/raidparts/designer/change-a-part).
4. **Mark the part.** Once a part has had any physical work, its number is written on it. See [Shop rules](https://docs.raidrobotics.org/raidparts/manufacturing/shop-rules).

## Why we use them

A name like "Standoff 1", "Lower standoff" or "Purple standoff" means different things to different people. `26-04103` means one part. Numbers also let RAIDParts link a design part to its manufacturing part, its MO and its label, and they build a habit that industry teams use every day.

CAM programs use a shorter form of the part number. See [CNC program numbers](https://docs.raidrobotics.org/raidparts/reference/cnc-program-numbers).


---

# 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/design/part-numbers-and-boms/part-numbers.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.
