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

# COTS and assembly readiness

## COTS parts

COTS (commercial off-the-shelf) parts are bought, not made. In a subassembly, click **COTS**, fill in the vendor, cost and quantities, then **Add COTS**. Change a line's status from its **Status** dropdown.

![A subassembly's COTS section, with a line in stock](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-80fa6c0b90e90d21e4f1ac91aff5055948d847f6%2Fdesign-cots.jpg?alt=media)

| COTS part status | Meaning                          |
| ---------------- | -------------------------------- |
| needed           | Not ordered yet                  |
| ordered          | On a purchase order              |
| received         | Arrived                          |
| in stock         | Stock covers the quantity needed |

## Purchase orders

Group COTS parts into purchase orders. You can also bring one in with **Import COTS order** from a spreadsheet.

Purchase order status: **draft**, **ordered**, **shipped**, **received**, **closed**.

{% hint style="info" %}
Marking a purchase order **received** puts all of its parts in stock.
{% endhint %}

## Assembly readiness

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

* every live design part is **manufactured**,
* every COTS item is **in stock**, and
* everything is kitted.

Click **Kit** once a part or COTS item is gathered for assembly. **Un-kit** reverses it, and the message that pops up offers **Undo**. Anything missing is listed as a blocker, with a link to the part in Design. The subassembly's own review status is shown but doesn't block readiness.

![Assembly readiness, listing parts not made and a COTS item not kitted](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-a5ec3e6a1092708227dacad0c59a463e1bf7d50b%2Fassembly-readiness.jpg?alt=media)

![COTS and assembly readiness](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-ff776a547911cdcb4dbf071b6afac024ff9ae160%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/raidparts/designer-guide/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.