Skip to content
  • guides
  • production flow

Production flow

A job in Eryxon Flow is not a static record — it flows. This page is the map of that flow, from the office creating the work to the floor finishing it. Each stage links to the feature that owns it.

The lifecycle

Section titled “The lifecycle”
flowchart TD
  J["Job created<br/>(customer, due date)"] --> P["Parts + routing operations<br/>(cell, sequence, planned time)"]
  P --> AS["Parts assigned to operators"]
  AS --> Q["Operation in the operator queue"]
  Q --> G{"Earlier operations<br/>on the part completed?"}
  G -->|yes| ST["Start → in_progress"]
  G -->|"no, Sequential release off"| ST
  G -->|"no, Sequential release on"| Q
  ST <-->|"pause / resume"| H["on_hold"]
  ST --> WK["Work: report issues,<br/>substeps, CAD"]
  WK --> CO["Complete → duration recorded"]
  CO -->|last operation on the part| PC["Part completed"]
  PC -->|all parts done| JC["Job completed"]
  CO -->|more operations| Q

Stages

Section titled “Stages”
  1. Job creation. An admin enters a job — customer, due date — then its parts (with material, quantity, drawings, and assemblies via parent/child parts) and each part’s operations. An operation carries the cell it runs at, a sequence, and a planned time. That routing is what the rest of the system reasons about.
  2. Assignment. Parts are assigned to operators; the operations then appear in those operators’ queues.
  3. Execution. An operator opens an operation, starts timing (status → in_progress), and works — pausing and resuming (on_hold), reporting issues, ticking off substeps, opening the drawing or 3D model. Completing stops the clock and records the actual duration. With Sequential release switched on in Organization settings, an operation cannot start until every earlier operation on the part is completed; the rule lives in the database, so the API and MCP server follow it too.
  4. Completion rolls up. When the last operation on a part completes, the part completes itself; when every part in a job completes, the job does too. No one closes it by hand.

Time tracking

Section titled “Time tracking”

Every start/stop writes a time entry against the operator and the operation, and pauses are tracked separately, so booked hours always reflect who did the work and for how long — not the shared terminal. See Time tracking on the operator terminal.

Where each stage lives

Section titled “Where each stage lives”