> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Production Technicians and Operators

> How floor operators use ION: daily dashboard, run execution, scanning parts, capturing data, and raising issues without leaving your workstation.

## What ION does for you

ION is your daily tool. The dashboard shows the day's work in priority order, assigned to you. You execute procedures step-by-step on the runs your supervisor (or scheduling) routed to your work center. You scan in parts, capture readings, attach photos, and when something's wrong on the floor, you file an issue *from inside the run*, no chasing supervisors, no separate paper form.

The goal is that you spend your time *building*, not navigating tools. If you find yourself doing more clicking than building, something is misconfigured upstream and your manufacturing engineer should hear about it.

## Where to start

1. **[Runs and Execution](/build-hardware/runs-and-execution)**: the operator-facing flow: open a run, work the steps, install parts, hit done.
2. **[Workcenter Execution](/build-hardware/runs-and-execution/workcenter-execution)**: kiosk mode and shared workstation patterns for teams.
3. **[Issues and NCRs](/track-quality/issues)**: how to raise a quality issue mid-run when something's wrong with a part or step.

## The handful of pages that matter most

| Page                                                                                        | Why it matters to you                                                            |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [Runs and Execution](/build-hardware/runs-and-execution)                                    | The exact flow of executing a run on the floor                                   |
| [Runs and Step States](/build-hardware/runs-and-execution/overview#states)                  | What "in progress", "blocked", "done" actually mean                              |
| [Editing Build Requirements](/build-hardware/bills-of-materials/editing-build-requirements) | Add or swap a part mid-run when the BOM is wrong for what you have on hand       |
| [Label Printing and Barcodes](/build-hardware/labels-and-scanning/printing)                 | Print serial labels and scan-in installs                                         |
| [Issue Lifecycle](/track-quality/issues/overview)                                           | What happens to an issue you raise: states, dispositions, who owns the next step |
| [Redlines and Deviations](/build-hardware/runs-and-execution/redlines-and-deviations)       | When the procedure doesn't match reality, this is the right channel              |

<Tip>
  * **Scan, don't type.** If your work center has a scanner, every install should be a scan. Typing serial numbers is the #1 source of bad data.
  * **File the issue *now*, not after the shift.** Issues filed in-context (right from the run step) carry the run, the step, the part, and the operator, all auto-populated. Issues filed after the fact need all that re-entered.
  * **Don't fight the procedure silently.** If a step is wrong, missing, or in the wrong order, file a redline. Quietly working around it leaves engineering with no signal that the procedure needs to change.
  * **The dashboard is your home.** Check it at the start of every shift. Priority and assignment shifts overnight.
</Tip>

## Related

* [Runs and Execution](/build-hardware/runs-and-execution)
* [Issues and NCRs](/track-quality/issues)
* [Labels and Scanning](/build-hardware/labels-and-scanning)
* [What is ION?](/)