> 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/cots-and-readiness.md).

# COTS and assembly readiness

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

## COTS parts

COTS (commercial off-the-shelf) parts are bought, not made. In a subassembly, click **COTS**, search the **Catalog part** box and pick the part, set the design quantity and spares, then **Add COTS**. Picking a catalog part fills in the name, part number and vendor.

Can't find it? Type the name in yourself and ask an admin to add the part to the [catalog](https://docs.raidrobotics.org/raidparts/inventory/catalog). A line that isn't linked to a catalog part can't have parts set aside for it. To link it later, click the line and pick the part.

Stock and ordering happen in the [Inventory](https://docs.raidrobotics.org/raidparts/inventory) environment, not here. Each COTS line shows how many are **set aside** for it out of how many it needs, and a status:

| Status                | Meaning                                                                                    |
| --------------------- | ------------------------------------------------------------------------------------------ |
| set aside on approval | Linked to the catalog. Parts are set aside when the subassembly is approved.               |
| set aside             | Its full quantity is set aside from stock.                                                 |
| short                 | The subassembly is approved but stock didn't cover the line. It's on Inventory › To order. |
| not in catalog        | Not linked to a catalog part, so nothing can be set aside.                                 |
| kitted                | Gathered for assembly and taken out of stock.                                              |

## Approval sets parts aside

When a subassembly is **approved**, Inventory sets aside what's free on the shelf for each of its linked COTS lines. Whatever is still short goes on **Inventory › To order** for whoever orders parts (Inventory users). Parts that arrive later go first to the subassembly approved earliest.

Sending a subassembly back with **Request changes**, making it obsolete or deleting it gives its set-aside parts back for the next subassembly in line. Changing a line's part or quantity on an approved subassembly sets aside again for the new amount.

If a part you no longer need is already on a draft order, deleting or lowering the line (or making the subassembly obsolete or deleting it) takes it back off that draft. Orders already placed with the vendor don't change.

## Import a COTS list

**Import COTS list**, under **Needs review** in the subsystem list, adds COTS lines to subassemblies from a spreadsheet (CSV). **Template** downloads one with the expected columns.

* Commas or semicolons both work. "Assembly #" is the subassembly number; "Assembly" is its name.
* Quantities must be whole numbers. Errors give the line number in your file.
* Duplicate rows for the same part are merged. A line already on the subassembly never needs fewer than it did.
* A part number that matches exactly one catalog part links the line to it.

## Assembly readiness

Open **Design › Assembly** (or **Manufacturing › Assembly**). A subassembly is ready when:

* every live design part is **manufactured**,
* every COTS item is set aside from Inventory (or already kitted), and
* everything is kitted.

Click **Kit** once a part or COTS item is gathered for assembly. Kitting a COTS item takes its set-aside parts out of stock; a COTS line can only be kitted once its subassembly is approved and all of its parts are set aside. **Un-kit** reverses it and puts the parts back where they came from, and the message that pops up offers **Undo**. Anything missing is listed as a blocker, with a link to the part in Design. A short COTS line says why, for example "short · 2/4 set aside". The subassembly's own review status is shown but doesn't block readiness.

![Design › Assembly, listing parts not made and a COTS line not set aside because it is not in the catalog](https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-5c291f2838d9e4890a63b4e02ced50b9755698e4%2Fassembly-readiness.jpg?alt=media)

![COTS and assembly readiness](https://3371293148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9qOZFPsH0lfSzbgmM0Zp%2Fuploads%2Fgit-blob-f927a65d0699b341ec0a834e460df0589db1dff8%2F09-cots-readiness.png?alt=media)


---

# 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/cots-and-readiness.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.
