Work order page
Actions
| Action | Who | Does |
|---|---|---|
| Release | planner | Snapshots the part's routing into this order's steps (or a single Build step when there is no routing) and opens it to the floor. Editing the routing later does not change this order |
| Cancel | planner | Closes an unfinished order |
| Create orders for components | planner | A draft work order for each component of this part that is made here (stocked, with a routing), at line quantity × this order's quantity, output to this order's component location, at this priority and due date. Phantoms are skipped — they are built inside this order. The first, manual cut of MRP explosion |
| BOM | The part's bill of materials | |
| Custom data | The order's opaque JSON |
Draft — edit, then release
Quantity, priority, due, the two locations and notes, while the order is a draft.
Order
Done of ordered, released and completed times, notes.
Reference is another system's name for what the job is about ("Hull 207"). It can be set or changed at any status, and the API can find orders by it. Foudra never interprets it.
When the part is not stocked, the order is a job rather than a build: the first row reads Job, and finishing the order puts nothing into stock. See services.
Extra parts
For a part the job needed that its bill of materials does not list: a replacement fitted during a service, something broken on assembly. While the order is released or in progress, an operator picks the part, a quantity and a reason, and Issue takes it from the order's component location (or beneath it) as a ledger movement referencing the order. Not enough on the shelf is refused, naming the part. Each issue is listed here.
Nothing else is needed to replace it: if the part has a minimum stock, the next planning run proposes making or buying another.
Steps
One card per step, in sequence, with its group, the station it is running on, its status and its done quantity.
Order names what the order makes, linked to the part, with done-of-quantity, the release and completion times and the notes. Order names what the order makes, linked to the part, with done-of-quantity, the release and completion times and the notes. Consumes lists the step's materials: the BOM lines allocated to this step (unallocated lines go to the first step), with phantoms expanded to what is actually on a shelf. Per unit, still required for the quantity this step has yet to do, on hand here at the order's component location or anywhere beneath it (an order drawing from a site can use every shelf in it), and a short flag. A step with no materials is pure labour.
| Badge | Meaning |
|---|---|
| ready | Pending, earlier steps done, nothing short |
| pending | Waiting on an earlier step or on materials |
| running | Started |
| done / skipped | Finished |
Scrap… records a run that made nothing — a unit that failed test, a print that came out wrong: materials for the quantity are consumed from the component location with the reason on the ledger rows, nothing is produced, and the step's count is unchanged.
Start (operator) puts the step on a workstation from its group and marks the station busy. Complete records a quantity — the whole remainder by default, less for a partial run — and backflushes: the step's materials for that quantity are issued from the component location or the locations beneath it, biggest pile first, as production_issue movements referencing the step, and on the last step the output is received into the output location. Not enough on the shelf refuses the completion naming the part. Skip passes a pending step without doing it.
The order completes when the last step's done quantity reaches the ordered quantity.