Jobs
Know where a job comes from, how it moves and how its minutes are measured.
Updated 23 September 2026
- Why
- A shop that cannot say where a job is or what it took cannot cost it.
- What
- A job is one unit of work at one machine, the same shape in every machine module.
- How
- The machine modules raise jobs as they plan work; a job moves by scans at the machine and carries a trace code from start to finish.
Where a job comes from
| Raised when | Machine module | Standard minutes from |
|---|---|---|
| A nest is approved or cut | Arcline | The nester's own time estimate |
| A run is queued or started | Wire EDM and CNC Milling | The run's modelled minutes from the chart |
| You ask the AI interface to make a job and confirm the action it offers | None (a manual job) | Nothing: it has no standard minutes and no machine |
A nest or a run is exactly one job: approving the same nest twice raises one. Nothing on the machine module screens changes; the job simply sits behind the nest or the run.
How a job moves
| Status | Means |
|---|---|
| Queued | Where every job starts: waiting on a machine, on the schedule |
| Draft | Taken back off the queue |
| Setting up | Setup minutes are being measured |
| Running | Run minutes are being measured |
| Paused | Stopped; a pause is not counted |
| Done, Scrapped or Cancelled | Finished; the job does not move again |
The moves happen on the station screen at the machine: Take this job, Start setting up, Start running, Pause, Finish and Scrap. Each move closes or opens the time segment and writes the trace event in one step; a pause or a finish also records the minutes on the costing ledger.
Minutes are measured, not typed
A job's actual minutes are the sum of its setup and run segments from the scans. Open a job from the schedule or the costs to see its Time and its Trail.
- Step 1.
Open the job from
/app/machinist/scheduleor/app/machinist/costs. - Step 2.
Under Correct the minutes, pick Setup or Run and enter the minutes.
- Step 3.
Say what happened in Why they are being corrected and choose Save.
A correction is stored as its own row, marked Typed in, with the reason. The scanned rows stay as they were. Corrections need the engineer role or above.
A machine station, 3-axis vertical machining centre 500, scanning job KAB-J26-00001 in and then out, each scan landing on the job's trail.
Station out: the minutes between are the job's time.