> 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/manufacturing-guide/your-station.md).

# Your station

## Open your station

1. Pick **Manufacturing** in the header and open the **Workstation** tab.
2. Choose your station: Bandsaw, CAM, CNC Router, Bend, Debur, Coating, QA, Manual Lathe, Print or Post Process. ![The station list](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-f635890364f3307640f4b9f890e0f6c88b0d7196%2Fworkstation-stations.jpg?alt=media)
3. On a shared tablet, click **Pin station**. The tablet stays on that station, even after a reload. Click **Unpin** to switch.

## The queue

Your station's queue lists every MO whose current step is at your station, in this order:

1. work already in progress,
2. then by priority: critical, high, medium, low,
3. then oldest first.

**Queue clear** means nothing is waiting at your station.

![The CAM station queue, with three MOs in progress](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-18ea9e9732343cf9dd41bd5dfbd8f210d7ca5b96%2Fworkstation-queue.jpg?alt=media)

## The work card

Tap an MO in the queue, or scan its QR label, to open its work card.

![A work card at CAM, showing the route, details, 3D model, Problem and CAM done](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-e24d2ea4fda0f3374cfc42997ac5881939e2ed6e%2Fwork-card.jpg?alt=media)

| Part of the card   | What it shows                                                                  |
| ------------------ | ------------------------------------------------------------------------------ |
| Header             | MO number, part number, subsystem, priority and status                         |
| Route              | Every station in order, with the current one highlighted and who is working it |
| Details            | What your station needs before touching the part (below)                       |
| Notes and 3D model | Notes, including QA rework reasons, and the STEP file viewer                   |
| Buttons            | **Problem**, **Start**, **done**, and **QA fail…** at QA                       |

### What each station sees

| Station         | Details                                                              |
| --------------- | -------------------------------------------------------------------- |
| Bandsaw         | Cut length                                                           |
| Manual Lathe    | Cut length, lathe drawing                                            |
| CAM, CNC Router | Thickness                                                            |
| Bend            | Number of bends, bend drawing (shows **Missing** if there isn't one) |
| Coating         | Color                                                                |

Next: [Work a step](/raidparts/manufacturing-guide/work-a-step.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/manufacturing-guide/your-station.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.