Skip to main content

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.

​
Overview

A run is one execution of a procedure against a specific part inventory. Starting a run is the moment a build moves from “planned” to “actively producing” — and it’s where you bind together three things that will travel through the rest of the build:
  • The procedure that defines what work will happen.
  • The part inventory the run produces (or, for a rework run, modifies).
  • The assignment — who’s doing the work, at which work center.
This page walks through creating a run from each of the common entry points.

​
Prerequisites

  • A released procedure for the target part.
  • A part inventory record for the unit being built (created automatically when the part is staged from receiving, kitting, or a parent run).
  • Permission to create runs in your organization.

​
Three ways to start a run

You’re starting from…Use this entry point
The procedureStart run button on the procedure page
The part inventory (e.g. just received a kit)Start run action on the inventory unit
A schedule (planned work)The scheduling board — see Scheduling and planning
Each path lands at the same end state: a Run record in Todo, ready for an operator to pick up.

​
Starting from a procedure

  1. Open the procedure.
  2. Click Start run.
  3. Select the part inventory the run will build.
  4. Set the run title (optional — defaults to a generated name like Run 1234: BRKT-ASSY-001 · SN-00001).
  5. Optionally pre-assign operator and work center.
  6. Click Create.
ION instantiates run steps from the procedure’s steps automatically. Each procedure step becomes a RunStep in todo state, in the same order, with the same fields and validations.

​
Starting from a part inventory

When you’re already looking at a part inventory unit (e.g. a serialized kit just released to the floor):
  1. Open the part inventory page.
  2. Click Start run.
  3. Select the procedure to execute.
  4. The part inventory is pre-filled.
  5. Set title and assignments as above.
  6. Click Create.
This is the most common path during operator handoff — the kit shows up on the floor, the operator finds it in ION, and starts the run from there.

​
Pre-run configuration

A few options are worth setting at run-creation time rather than mid-run:

​
Run batch

If this run will be batched with other runs of the same procedure, set the run batch at creation. Steps in batched runs propagate sign-offs and redlines together — see Run Batches. You can add a run to a batch later, but doing it upfront avoids divergence between batched and unbatched siblings.

​
Assignment

Pre-assigning an operator and work center makes the run discoverable on their own work view. If you don’t pre-assign, the run lives in the org’s “unassigned” pool until someone picks it up.

​
Title

The default title encodes the run ID and target part. If your org tracks builds by a different identifier (customer PO, lot, build number), put it in the title — it’s the first thing operators see in any list view.

​
What ION does on run create

When createRun succeeds, ION:
  1. Creates the Run record in Todo.
  2. Copies the procedure’s steps into RunStep records, preserving order, fields, and validations.
  3. If the procedure has step-level approval gates, instantiates the corresponding gates on the run steps.
  4. Captures the procedureId and procedureRevision — this run is bound to that exact revision, even if the procedure is later revised.
  5. Snapshots applicable build requirements from the part’s mBOM into the run’s aBOM.
Procedure revision is locked at run-create time. If you revise the procedure mid-run, in-flight runs continue executing the version they were created with. New runs pick up the new revision.

​
Troubleshooting

“No procedures available for this part” — the part doesn’t have any procedures associated. Either (a) link the procedure to the part in the procedure record, or (b) start from the procedure side and pick the part inventory. “Part inventory is not in a state that allows a new run” — the inventory unit is consumed, installed, or scrapped. You can’t start a build run on inventory that’s already been used. Check the inventory’s state on the inventory page. “Procedure has unreleased steps” — the procedure isn’t in released state, or some of its steps aren’t approved. Release the procedure first, then start the run.

​
Programmatic creation

For integrations that schedule runs from an external system (MES, ERP, custom dispatcher), see Common Queries → Create a Run.

​
Tips

  • Set title to something operators search for. If the floor team looks up runs by lot or PO, put that in the title. The auto-generated Run 1234 is fine for the API but easy to lose in a list view.
  • Pre-assign when possible. Even tentative pre-assignment (you can reassign later) puts the run in the right person’s view.
  • Don’t start runs you can’t finish that day. A run sitting in In Progress overnight isn’t bad, but a run sitting in In Progress for a week without step activity usually means it should have been planned differently.