> 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/reference/terminology.md). # Terminology The words RAIDParts shows on screen, in one place. The docs, training decks and process maps use these exact labels, so what you read matches what you click. ## Roles | Role | What they do | | ------------ | ------------------------------------------------------------------------------------------------------------------- | | Designer | Builds the Design BOM, submits parts for review, and creates the manufacturing part once a design part is approved. | | Reviewer | Any designer reviewing someone else's part. You can't approve your own part (admins can). | | Manufacturer | Works MOs at the stations, reports problems and runs QA. | | Admin | Everything above, plus users, holds, seasons and the Library. | A person can hold any combination of roles. To create parts, a designer also needs access to the Manufacturing environment. ## Where things are | Environment | Tabs or sections | | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | Design | Bill of materials, Assembly readiness | | Manufacturing | Parts, Workstation, Production, Assembly, Labels (admins) | | Admin | Operations: Holds, Labels to print, MO History, Seasons, Subsystems. Library: Colors, Base materials, Materials, Thicknesses. Team: Users | ## Design part status | On screen | Meaning | | ----------------- | ----------------------------------------------------------------------- | | draft | Being written. Not yet submitted. | | submitted | Waiting for a reviewer. | | in review | A reviewer has started. | | changes requested | The reviewer asked for changes. Fix it and **Submit for review** again. | | approved | Ready for a designer to **Create part**. | | in manufacturing | The part has been created and has an MO. | | manufactured | QA passed on its MO. | | obsolete | No longer used. | Review buttons: **Submit for review**, **Start review**, **Approve**, **Request changes** (needs a comment). ## MO status | On screen | Meaning | | ---------------------------- | ------------------------------------------------------------------------------- | | Queued | No step started yet. | | Working | At least one step has started. | | Waiting QC | QA is the next step. | | Completed | Every step is complete. | | Canceled | Stopped by an admin. Kept for records. | | On hold · Cancel requested | Someone asked to cancel. Nobody works it until an admin decides. | | On hold · Obsolete requested | The design part is being made obsolete. Nobody works it until an admin decides. | ## Step status | On screen | Meaning | | ----------- | ----------------------------------------------------------------- | | Pending | Waiting in the station queue. | | In progress | Someone has started it. The work card shows who and for how long. | | Complete | Done. | ## Shop-floor buttons | Button | What it does | | ------------------- | ------------------------------------------------------------------------ | | **Start (station)** | Starts the current step. | | **(Station) done** | Completes the step. A toast offers **Undo**. | | **Take over** | Starts a step someone else has in progress, after you confirm. | | **QA pass** | Completes QA and the MO. | | **QA fail…** | Opens a dialog to pick an earlier step, then **Send back to (station)**. | | **Problem** | Opens the problem dialog; pick a reason, then **Report problem**. | | **Resolve** | Clears a problem. Admins, or the person who reported it. | Problem reasons: Wrong dimensions, Material problem, Missing or wrong drawing, Machine down, Something else (needs a note). ## Design and part buttons | Button | What it does | | -------------------------------- | -------------------------------------------------------------------------------- | | **+ Assembly** / **+ Part** | Add a subassembly / a design part in the Bill of materials. | | **Comment** | Posts to a part's or subassembly's thread. | | **COTS**, then **Add COTS** | Adds a bought part to a subassembly. | | **Import COTS order** | Brings in a purchase order from a spreadsheet. | | **Create part** | Turns an approved design part into a part and its MO. | | **Edit part** / **Done editing** | Turns field editing on and off in a part's details (part's designer and admins). | | **Update MO** | Applies part changes to an open MO that's **Out of date**. | | **Kit** / **Un-kit** | Marks a part or COTS item as gathered for assembly. | ## Holds and cancels | Button or label | Who | What it does | | ----------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Request cancel** | Manufacturer | Puts the MO on hold until an admin decides. A reason is required. | | **Cancel MO** | Admin | Cancels the MO right away. | | **Make obsolete** | Designer | Then **Mark obsolete** (applied right away if the part hasn't been created) or **Send request** (part already created: the part and its MOs go on hold). | | **Delete** | Admin | Then **Delete part**. Deletes the design part and any manufacturing part. | | **Approve cancel** | Admin | Order holds: cancels the MO. | | **Approve obsolete** / **Approve delete** | Admin | Part holds: cancels open MOs, then marks the design part obsolete or deletes it. | | **Release hold** | Admin | Clears the hold. | | **On hold** | Everyone | A request is waiting on an admin. Don't work it. | | **Canceled** | Everyone | The MO is stopped for good. Never shown as On hold. | | **Obsolete** | Everyone | The part was retired and its open MOs canceled. An admin can restore it from the Design BOM. | ## COTS | Thing | Statuses | | ------------------- | ----------------------------------------- | | COTS part | needed, ordered, received, in stock | | COTS purchase order | draft, ordered, shipped, received, closed | Marking a purchase order received puts its parts in stock. **Kit** marks a part or COTS item as kitted. ## Words we use the same way everywhere * **MO** (manufacturing order). Say "MO", not "order" or "job". * **Part** is the manufacturing part. **Design part** is the BOM entry it comes from. * **Station** is where work happens. **Step** is one station's work on one MO. * **Create part**: always the Designer, from an approved design part. * **Assembly ready**: every live part made, every COTS item in stock, everything kitted. --- # 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/reference/terminology.md?ask=&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.