Manufacturing
This page is generated from the in-app guide content — edit
featureToggleGuidesand runpnpm gen:feature-toggle-docs.
Assign production work to production personnel only
Crews, operation assignment and the people on production reports only accept employees in the Production personnel list. Operators who start a step themselves are not blocked; reports flag them as not in the list. Requires production crews and operator skills.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.personnel_roster_only | Off | /manufacturing/settings | Production crews and operator skills (manufacturing.labor_skills) |
How it works
Read when crew members are saved, when a step is assigned to a person, when a production report lists people, and by the operator picker of a step.
Conditions for it to take effect
Production crews and operator skills must be on.
When ON
Pickers show production personnel only, and the server refuses anyone else with a clear error. People with the step’s work center as home work center are listed first.
When OFF
Any active employee can be added to a crew or assigned (default). The Production personnel list still exists and feeds the By-employee report.
Screens, documents and reports affected
Crew dialog, Assign on the shop floor board, people on production reports.
Caveats
Existing crew members who leave the list stay in their crew — only new members are checked. The list was pre-filled with people who already worked in production in the last 12 months; review it before turning this on.
Example
A 300-person company keeps 40 people in production personnel; the crew dialog and assignment only show those 40.
Block release on material shortage
When the material reservation cannot cover every line, refuse to confirm the work order instead of confirming it with a shortage warning.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.block_release_on_shortage | Off | /manufacturing/settings | Reserve materials on release (manufacturing.reserve_materials) |
How it works
Checked when a work order is confirmed, inside the same transaction as the reservation, and as a pre-check before the order is sent for approval.
Conditions for it to take effect
Reserve materials on release must be on; without it there is no reservation to compare and this toggle has no effect.
When ON
Confirming a work order whose reservation cannot cover every line is refused with the missing material listed.
When OFF
The order is confirmed with a shortage warning. Off by default for existing and new tenants.
Screens, documents and reports affected
Confirm action on the work order, submit for approval.
Caveats
An order confirmed by an approval workflow is not blocked at the moment of approval (the check runs when it is submitted) — stock taken between submit and approval can still leave it short. Nothing is stored by this toggle, so turning it off has no clean-up.
Example
Use it when a started order that waits for materials ties up machines and labor; leave it off if you prefer to confirm early and chase purchases.
BOM & routing revisions
Draft → released (locked) → obsolete revisions for BOMs and routings; work orders keep the revision they were created from. Requires standalone routings.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.bom_revisions | Off | /manufacturing/settings | Standalone routings (manufacturing.routings) |
How it works
Read when a BOM or routing revision is released or a new revision is started.
Conditions for it to take effect
Standalone routings must be on.
When ON
BOMs and routings go draft → released (locked) → obsolete; editing a released one means starting a new revision. Work orders keep the revision they were created from.
When OFF
A BOM or routing is one editable version; release / new revision actions are refused. Off by default for existing and new tenants.
Screens, documents and reports affected
Revision panel on BOM and routing detail.
Caveats
Turn off ECO first. Draft revisions left when you turn it off cannot be released until you turn it back on; released revisions stay locked.
Example
Revision B of a PCB swaps a capacitor; orders already running stay on revision A, new orders use B.
Downtime tracking
Record planned and unplanned stops per work center or machine with a reason code. Off = no Downtime page.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.downtime | Off | /manufacturing/settings | — |
How it works
Every downtime action (list, record, edit, stop, request repair, delete) checks it in the transaction.
When ON
Record planned and unplanned stops per work center or machine with a reason code; open stops block capacity on the schedule and feed OEE.
When OFF
No Downtime page; all downtime actions, including stopping an open event, are refused. Off by default for existing and new tenants.
Screens, documents and reports affected
Downtime menu and page, schedule capacity, machine status, OEE and overview cards.
Caveats
Turn off OEE and asset maintenance link first. Close open stops before turning it off. While off, the schedule ignores stop records, but a machine left Down keeps that status — set it back on the machine page. Stops still open reappear when you turn it back on.
Example
Press 2 jams at 10:05: record an unplanned stop ‘mechanical’, close it at 10:40 — the schedule shifts and OEE availability drops.
Engineering change orders (ECO)
Propose a change with reason, effective date and how to handle open work orders and stock; approve it through a workflow, then apply it to release the new revision. Requires revisions.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.eco | Off | /manufacturing/settings | BOM & routing revisions (manufacturing.bom_revisions) |
How it works
Read when an engineering change order is created, submitted and applied; while on, releasing revision 2 or later directly is refused — it must come from an ECO.
Conditions for it to take effect
BOM & routing revisions (and therefore standalone routings) must be on.
When ON
A change is proposed with reason, effective date and how to treat open work orders and stock, approved through a workflow, then applied to release the new revision.
When OFF
Revisions are released directly; creating, submitting and applying ECOs is refused. Off by default for existing and new tenants.
Screens, documents and reports affected
ECO menu and pages (permission manufacturing:engineering), release button on BOM and routing revisions.
Caveats
Apply or cancel open ECOs before turning it off. Once off, draft revisions attached to an open ECO are no longer locked and can be released directly; ECOs can only be cancelled. An approval workflow that finishes after the toggle is off still records approved/rejected on the ECO, but it cannot be applied.
Example
Quality asks to change a gasket material: the ECO says ‘use up stock, change open orders from next week’, the engineering manager approves, apply releases revision C.
Finite-capacity production scheduling
Schedule work-order operations on work centers against HR calendars, holidays, parallel machines and step order, with a Gantt board, optimizer plans and pinning. Off = schedule entries are entered by hand as before.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.finite_scheduling | Off | /manufacturing/settings | — |
How it works
Read when the optimizer creates plans and when a solver plan is applied.
When ON
The optimizer schedules work-order operations on work centers against HR calendars, holidays, parallel machines and step order, and proposes plans you can apply; pinned bookings are kept.
When OFF
The schedule board still works by hand (drag, move, unplace, pin); only optimizer plans are unavailable. Off by default for existing and new tenants.
Screens, documents and reports affected
Optimizer on the schedule board, material-aware scheduling.
Caveats
Turn off Material-aware scheduling first. Bookings already placed stay and can still be moved by hand.
Example
Monday morning: run the optimizer for the week, pin the rush order, apply — the Gantt shows every operation per machine.
Hold finished goods for quality check
Finished / semi-finished goods received from a production report are put on hold (not sellable or issuable) until an inspector decides Pass (release, and reserve for the sales order on make-to-order) or Fail (keep on hold and raise an NCR).
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.output_qc_hold | Off | /manufacturing/settings | — |
How it works
Read inside the transaction of every production report (manual, automatic on completion, subcontract receipt).
When ON
Finished / semi-finished goods received from the report are put on hold — not sellable or issuable — and an output inspection opens. Pass releases them (and reserves them for the sales order on make-to-order); Fail keeps them on hold and raises an NCR.
When OFF
Output is available as soon as it is received. Off by default for existing and new tenants.
Screens, documents and reports affected
Production report, stock availability of finished goods, inspections in the Quality app, make-to-order reservation.
Caveats
Goods already on hold stay on hold after you turn it off until an inspector decides — clear pending output inspections first.
Example
Food production: every batch waits for the lab result before it can be shipped.
Link machine downtime to asset maintenance
When a maintenance record or work order in Asset Management starts on an asset linked to a machine, the machine is marked under maintenance and a downtime event opens automatically (planned for scheduled/preventive work, unplanned for corrective/emergency); completing or cancelling it closes the event. Machine status Down/Maintenance can no longer be set by hand. Requires downtime tracking and machines.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.asset_maintenance_link | Off | /manufacturing/settings | Downtime tracking (manufacturing.downtime) |
How it works
Read inside the Asset Management transaction when a maintenance record or asset work order on an asset linked to a machine starts, completes or is cancelled; it acts only when downtime tracking and machines are also on.
Conditions for it to take effect
Downtime tracking must be on; machines must also be on for anything to happen (the settings page only enforces downtime).
When ON
Starting maintenance marks the machine Under maintenance and opens a downtime event (planned for scheduled/preventive work, unplanned for corrective/emergency); completing or cancelling it closes the event. Machine status Down / Maintenance can no longer be set by hand.
When OFF
Asset maintenance does not touch machines; machine status is set by hand. Off by default for existing and new tenants.
Screens, documents and reports affected
Asset maintenance and asset work orders, machine status, downtime events, schedule capacity.
Caveats
After turning it off, downtime opened by maintenance is no longer closed automatically when the work finishes — stop it by hand on the Downtime page and set the machine status back on the machine page.
Example
Preventive maintenance on press 3 starts at 08:00: the press drops off the schedule with a planned stop and comes back when the technician completes the work order.
Lot/serial genealogy
Tracked materials must be consumed by lot/serial and linked to the output lots/serials, so you can trace backward to suppliers and forward to customers. Requires partial execution.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.genealogy | Off | /manufacturing/settings | Partial execution (issues, reports) (manufacturing.partial_execution) |
How it works
Read when materials are issued and when a production report is saved (both in the transaction), and by the traceability screen.
Conditions for it to take effect
Partial execution must be on.
When ON
Lot/serial-tracked materials must be issued and consumed by lot/serial and are linked to the output lots/serials, so you can trace back to suppliers and forward to customers.
When OFF
No lot links are written; a report that sends consumed lots is refused and the Traceability page is unavailable. Off by default for existing and new tenants.
Screens, documents and reports affected
Traceability menu and page, lot picker when issuing, lot fields when completing a step (web and mobile shop floor).
Caveats
Links recorded earlier stay in the database but are hidden while off, and reports made while off leave a gap in the chain that cannot be filled later.
Example
A customer reports a bad batch: trace finished lot FG-0412 back to resin lot R-77 from supplier X, then forward to every customer who received R-77.
Machines
Machines under each work center with cycle time or speed, batch size, setup and status; active machines become scheduling lanes and maintenance windows are excluded. Off = parallel machine count on the work center.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.machines | Off | /manufacturing/settings | — |
How it works
Every machine screen and action checks it; the scheduler reads it to decide its lanes.
When ON
Machines under each work center with cycle time or speed, batch size, setup and status; active machines become scheduling lanes and maintenance windows are excluded.
When OFF
Machine pages are unavailable and the scheduler uses the work center’s parallel machine count; machine data is kept. Off by default for existing and new tenants.
Screens, documents and reports affected
Machines menu and pages, machine fields on work centers, scheduling lanes, linked machine card on assets.
Caveats
While off, downtime is recorded per work center only (no machine picker). Linking downtime to asset maintenance needs this toggle on as well as downtime.
Example
Work center ‘CNC’ has three machines with different speeds; the schedule puts the long job on the fastest one.
Material-aware scheduling
The scheduler does not place the first operation before the expected material arrival; orders with unknown arrival are flagged short. Requires finite scheduling.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.material_aware_scheduling | Off | /manufacturing/settings | Finite-capacity production scheduling (manufacturing.finite_scheduling) |
How it works
Read when the scheduler loads its data; only takes effect while finite scheduling is also on.
Conditions for it to take effect
Finite-capacity production scheduling must be on.
When ON
The scheduler does not place an order’s first operation before its expected material arrival; orders with unknown arrival are flagged short.
When OFF
Material readiness is ignored when scheduling. Off by default for existing and new tenants.
Screens, documents and reports affected
Optimizer plans and material warnings on the schedule board.
Caveats
Arrival dates come from open purchase orders and work orders — keep their dates current or orders get flagged short. Nothing is stored, so turning it off needs no clean-up.
Example
Steel arrives Thursday: the cutting step of that order is placed Thursday afternoon, not Monday.
MRP & production planning
Forecast plan, MRP runs over the BOM (multi-level when that toggle is on) netting stock, open POs/requisitions/work orders, lot sizing and lead time. Planners pick suggestions to create draft work orders and purchase requisitions — nothing is created automatically. Off = no Planning page.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.mrp | Off | /manufacturing/settings | — |
How it works
Every planning endpoint (plans, policies, runs, suggestions, convert) checks it.
When ON
Forecast plans and MRP runs over the BOM (multi-level when that toggle is on), netting stock, open purchase orders/requisitions/work orders, with lot sizing and lead time. Planners pick suggestions to create draft work orders and purchase requisitions — nothing is created automatically.
When OFF
No Planning page; planning calls are refused with “feature disabled”. Off by default for existing and new tenants.
Screens, documents and reports affected
Planning menu and pages (permission manufacturing:planning), MRP report tab.
Caveats
Turning it off hides plans, runs and suggestions but keeps them; draft work orders and requisitions already converted are ordinary documents and stay.
Example
Monthly forecast of 2,000 chairs: the run nets 300 in stock and 500 on open orders and suggests a 1,200-chair work order plus a requisition for the missing wood.
Multi-level BOM
Sub-assemblies, phantom and by-product lines, BOM status and effectivity, where-used and standard cost roll-up. Work orders consume what the BOM explosion says (by-products are never consumed). Off = single-level BOMs as before.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.multi_level_bom | Off | /manufacturing/settings | — |
How it works
Every BOM explosion (work order consumption, child orders, MRP, standard cost) goes through one explosion service that reads this toggle; BOM create/update refuse multi-level fields while it is off.
When ON
BOM lines can be sub-assemblies, phantoms or by-products; a BOM has status and effectivity dates, where-used and a standard cost roll-up. Work orders consume what the explosion returns — by-products are never consumed. Cycles between BOMs are refused.
When OFF
Single-level BOMs as before. Saving a BOM with multi-level fields, or replacing BOM lines through the update call, is refused with “feature disabled” (header edits still work). Off by default for existing and new tenants.
Screens, documents and reports affected
New BOM form and BOM detail (line types, status, effectivity, cost roll-up), new work order form, work center defaults, MRP.
Caveats
Turning it off does not change existing data: phantom/sub-assembly lines and child orders already created stay, but new explosions read only one level, so a BOM that relies on phantoms may consume the phantom item itself. Finish open multi-level orders first.
Example
A bicycle BOM with a wheel sub-assembly and a phantom ‘hardware kit’: the work order consumes the kit’s screws directly and a child order makes the wheels.
OEE
Availability × performance × quality per work center or machine, compared with the OEE target. Requires downtime tracking.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.oee | Off | /manufacturing/settings | Downtime tracking (manufacturing.downtime) |
How it works
Read by the OEE report, its Pareto and the overview/report tab cards.
Conditions for it to take effect
Downtime tracking must be on.
When ON
Availability × performance × quality per work center or machine, compared with the OEE target, with a Pareto of stop reasons.
When OFF
No OEE page or cards. Off by default for existing and new tenants.
Screens, documents and reports affected
OEE menu and page, OEE report tab (permission analytics:manufacturing), overview OEE card.
Caveats
Read-only: turning it off removes nothing. Numbers are only as good as the stops and reports recorded.
Example
Line 1: 90% availability × 85% performance × 98% quality = 75% OEE against an 80% target.
Operators missing a required skill
What happens when a step is assigned to, or started by, someone who lacks a competency at the level the step requires. Warn lets it through with a notice; Block refuses it.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.skill_gate | warn | /manufacturing/settings | — |
How it works
Read on assign and start of a shop floor step, only while Production crews and operator skills is on.
Conditions for it to take effect
Takes effect only when Production crews and operator skills is on.
When ON
Block: assigning or starting a step for someone below the required competency level is refused.
When OFF
Warn (default): the action goes through and the missing skills are shown as a warning. Any value other than Block behaves as Warn.
Screens, documents and reports affected
Assign and Start on the shop floor (web and mobile).
Caveats
Nothing is stored by this setting, so switching it has no clean-up; steps already running are not re-checked.
Example
Start with Warn while HR fills in the competency matrix, switch to Block once it is complete.
Partial execution (issues, reports)
Issue materials in batches with over-issue approval, return materials, report output partially with lots/serials and scrap, child orders for sub-assemblies. Journal per document. Off = start issues everything, completion receives everything.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.partial_execution | Off | /manufacturing/settings | — |
How it works
Read inside the transaction by every manual execution document: material issue, over-issue decision, material return, production report, child orders and make-to-order links on a work order.
When ON
You issue materials in as many batches as needed (over-issue beyond the BOM quota waits for approval), return unused materials, report output in parts with lots/serials and scrap, and create child orders for sub-assemblies. Each document posts its own journal entry. Work orders can be closed.
When OFF
Auto mode: starting a work order issues the whole remaining quota, completing it reports the whole remaining quantity, cancelling it voids those automatic issues. Manual issue/return/report endpoints refuse with “feature disabled”. Off by default for existing and new tenants.
Screens, documents and reports affected
Execution panel on the work order (issue, return, report), child-order and sales-order fields on the new work order form, mobile production report, and the toggles that need it: shop floor, subcontracting, rework, genealogy.
Caveats
Turn off the dependent toggles first (shop floor, subcontracting, rework, genealogy) — the settings page refuses otherwise. Orders already partly issued switch to auto mode, so their next start/complete issues or reports the remainder automatically. Pending over-issue requests can still be rejected (approving needs the toggle) and production reports can still be voided. Return leftover materials before turning it off: in auto mode cancelling an order voids its issues (material goes back to stock), and material returns are not available.
Example
A batch of 1,000 units is made over three shifts: issue materials per shift, report 300 / 350 / 350 with their lots, then close the order.
Product costing (monthly)
Monthly job costing: materials from the stock ledger, labor (reported hours or closed payroll), overhead from the workshop cost centers’ GL, ending WIP, the cost transfer entry by accounting standard and re-pricing of finished-goods receipts. Off = no Product costing page; WIP left on a completed order is settled to variance as before.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.production_costing | Off | /manufacturing/settings | — |
How it works
Read by the Product costing pages (calculate, close, reopen a period) and by the journal listener that re-prices finished-goods receipts.
When ON
Monthly job costing: materials from the stock ledger, labor from reported hours or closed payroll, overhead from the workshop cost centers’ ledger, ending WIP, the WIP transfer entry by accounting standard and re-pricing of finished-goods receipts.
When OFF
No Product costing page; WIP left on a completed order is settled to variance when the order completes. Off by default for existing and new tenants.
Screens, documents and reports affected
Product costing menu and pages (permission manufacturing:costing), finished-goods receipt cost, landed cost allocation to work orders.
Caveats
Closed periods keep their entries; after turning it off you can still reopen a closed period or finish one stuck halfway through closing, but not calculate or close a new one. Pick one method per year — switching mid-year mixes settle-on-completion and period costing.
Example
End of March: calculate, review the job cards, close — the 154 → 155 transfer and finished-goods re-pricing post in one step.
Production crews and operator skills
Group operators into production crews, declare the competencies and headcount each routing step needs, and assign steps to a person or a crew on the shop floor. Labor minutes count every person on the step. Skills come from the HR competency matrix. Requires the shop floor.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.labor_skills | Off | /manufacturing/settings | Shop floor & operation tickets (manufacturing.shop_floor) |
How it works
Read by crew management, by assigning a step to a crew, by the skill check on assign/start, and when routing steps save competencies and headcount.
Conditions for it to take effect
Shop floor (and therefore partial execution) must be on.
When ON
Group operators into crews, declare the competencies and headcount each routing step needs, assign steps to a person or a crew; labor minutes count everyone on the step. Skills come from the HR competency matrix; what happens when someone lacks one is set by ‘Operators missing a required skill’.
When OFF
No crews and no skill checks; competency and headcount on routing steps cannot be changed. Off by default for existing and new tenants.
Screens, documents and reports affected
Crews menu and page, assignment on the shop floor board, competency fields on routing steps.
Caveats
After turning it off you can still remove a crew from a step, but not assign one. Competencies already copied to work orders stay but are ignored.
Example
The welding step needs 2 people with ‘MIG welding level 3’: assign crew W2, start is refused for a level-1 operator when the skill rule is Block.
Production versions (manufacturing templates)
Reusable templates for work orders: pin a BOM (fixed revision or latest released) and a routing, set validity dates, lot size range, priority, default warehouses, lead time and instructions. Work orders created from a version copy its structure at creation time. Off: work orders are created straight from a BOM as before.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.production_versions | Off | /manufacturing/settings | — |
How it works
Read on every production version screen and when a work order is created (manual, child order, MRP conversion).
When ON
Reusable templates pin a BOM (fixed revision or latest released) and a routing, with validity dates, lot size range, priority, default warehouses, lead time and instructions. A new work order picks or resolves a version and copies its structure at creation time; lot size outside the range shows a warning. MRP chooses the BOM by version.
When OFF
Work orders are created straight from a BOM; a work order sent with a production version is refused. Off by default for existing and new tenants.
Screens, documents and reports affected
Production versions menu and pages, version picker and lot-size warning on the new work order form, MRP.
Caveats
Existing work orders keep the version and pinned routing they were created with, even after you turn it off. A version that pins a routing needs Standalone routings on to create orders.
Example
Line A (fast, lots 500–2,000) and line B (manual, lots under 500) for the same product: the planner enters 300 and the line B version is chosen.
QC steps use Quality inspection templates
A quality-check step can carry an inspection template from the Quality app. Starting the step opens a pending inspection; its final result (with min/max checks) becomes the step result, and a failed inspection raises an NCR. Quick pass/fail entry is locked for such steps.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.qc_inspection_templates | Off | /manufacturing/settings | — |
How it works
Read when a QC operation is updated, when a production report is saved and when a work order completes (in the transaction).
When ON
A quality-check step can carry an inspection template from the Quality app. Starting the step opens a pending inspection; its final result (with min/max checks) becomes the step result, a failed inspection raises an NCR, and quick pass/fail entry is locked. The work order cannot complete while such inspections are unfinished.
When OFF
QC steps take a quick pass/fail; templates attached to steps are ignored. Off by default for existing and new tenants.
Screens, documents and reports affected
QC steps on the work order and shop floor, inspections in the Quality app.
Caveats
Inspections already opened from a step still lock its manual result after you turn it off — finish them in the Quality app. Templates can be attached to routing steps while off, ready for when you turn it on.
Example
The ‘final dimension check’ step uses template DIM-01 with 5 measurements; one value out of tolerance fails the step and opens an NCR.
Reserve materials on release
Confirming a work order reserves the material still to be issued at the role warehouse, so sales orders and other work orders cannot take it. The reservation shrinks as materials are issued, grows back when an issue is voided or materials are returned, and is released when the order completes or is cancelled. Not enough stock ⇒ reserve what is available and report the shortage. Off = no reservation.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.reserve_materials | Off | /manufacturing/settings | — |
How it works
Each time a work order’s status or material demand changes (confirm, issue, close, cancel, quantity edits), the material still to be issued is reserved at the role warehouse. Changing the toggle re-syncs every open order of the company.
When ON
Confirmed work orders hold their remaining material so sales orders and other work orders cannot take it. Issuing shrinks the hold, voiding an issue or returning material grows it back, completing or cancelling releases it. When stock is short the order reserves what exists and shows the shortage.
When OFF
No reservation; any order can take the stock. Turning it off releases every work-order reservation. Off by default for existing and new tenants.
Screens, documents and reports affected
Reservations card on the work order’s Materials tab, available stock seen by sales orders and other work orders.
Caveats
The re-sync when you flip the toggle runs over every open order in batches; an order that fails is logged and catches up the next time its demand changes — open its Materials tab to check. Block release on shortage depends on this toggle.
Example
Two orders need the same 500 kg of resin: the first confirmed holds it, the second shows a 500 kg shortage instead of both starting and stalling.
Rework orders
Create rework work orders from a non-conformance or a defect report line; their cost is added to the original order. Requires partial execution.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.rework | Off | /manufacturing/settings | Partial execution (issues, reports) (manufacturing.partial_execution) |
How it works
Read when a rework order is created and by the rework list and candidates.
Conditions for it to take effect
Partial execution must be on.
When ON
Create a rework work order from a non-conformance (NCR) or a defect line of a production report; its cost rolls up to the original order.
When OFF
No Rework page; creating rework orders is refused. An NCR disposition of ‘rework’ is then only a label. Off by default for existing and new tenants.
Screens, documents and reports affected
Rework menu and page, ‘Create rework’ link on NCRs and reports, rework KPI on the Quality report tab.
Caveats
Rework orders already created remain ordinary work orders you can run and complete from the work order list; their cost still rolls up to the original order.
Example
40 units fail final inspection: the NCR creates a rework order for 40 units, its labor and parts are added to the original order’s cost.
Shop floor & operation tickets
Operators start, pause and complete operations on a tablet screen; actual minutes come from the time log and completion posts a production report. Requires partial execution.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.shop_floor | Off | /manufacturing/settings | Partial execution (issues, reports) (manufacturing.partial_execution) |
How it works
Every shop floor action (queue, start, pause, resume, complete, assign) checks this toggle and partial execution; while on, the generic operation edit can only set pending or skipped.
Conditions for it to take effect
Partial execution must be on.
When ON
Operators start, pause and complete operations on the shop floor screen (web or mobile workforce app); minutes come from the time log and completing posts a production report. My work lists steps assigned to me.
When OFF
Operation status is changed from the work order as before; shop floor and My work are unavailable. Off by default for existing and new tenants.
Screens, documents and reports affected
Shop floor and My work menus and pages, mobile workforce shop floor, operation status on the work order.
Caveats
Turn off Production crews and operator skills first. Operations running or paused when you turn it off can be finished from the work order: changing their status closes the open time log, and completing them takes actual minutes from the logged time.
Example
An operator scans the work order on a tablet, taps Start, pauses for a material wait, taps Complete with 48 good / 2 scrap — the report and labor minutes post automatically.
Standalone routings
Routings become their own records shared by many BOMs, with ordered steps, work center/machine, setup and run times, QC gates and instructions. Off = steps are kept inside each BOM as before.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.routings | Off | /manufacturing/settings | — |
How it works
Read when a routing is created, edited or released, when a BOM’s routing is saved, and when a work order copies its operations.
When ON
Routings are their own records shared by many BOMs: ordered steps, work center/machine, setup and run times, QC gates and instructions. New work orders copy their operations from the BOM’s routing.
When OFF
Steps live inside each BOM as before; routing create/edit/release is refused with “feature disabled”. Off by default for existing and new tenants.
Screens, documents and reports affected
Routings menu and pages, routing editor on the BOM, routing status badge, production versions that pin a routing.
Caveats
Turn off BOM revisions (and ECO) first. After turning it off, new work orders take their steps from the steps stored inside the BOM; a BOM that only has a standalone routing keeps using that routing’s steps (read-only). Work orders created earlier keep the steps they copied. Production versions that pin a routing cannot create work orders while this is off.
Example
Ten paint colours share one ‘cut → weld → paint → pack’ routing; changing the weld time once updates every BOM.
Subcontracting
Routing steps can be outsourced to a subcontractor: a service purchase order linked to the work order, material sent to the partner’s transit warehouse, and a subcontract receipt that consumes material at the partner and receives the output in one step. The subcontracting fee is charged to the work order’s WIP when the vendor bill is posted. Requires partial execution.
| Code | Default | Switch at | Turn on first |
|---|---|---|---|
manufacturing.subcontracting | Off | /manufacturing/settings | Partial execution (issues, reports) (manufacturing.partial_execution) |
How it works
Read by every subcontracting action (service PO for an operation, send/return material to the partner, subcontract receipt and its void) and when a purchase order with lines tied to a work order is created or edited.
Conditions for it to take effect
Partial execution must be on.
When ON
A routing step can be outsourced: a service purchase order linked to the work order operation, material moved to the partner’s transit warehouse, and a subcontract receipt that consumes material at the partner and receives the output in one step. The fee goes to the work order’s WIP when the vendor bill is posted.
When OFF
Subcontracting actions are refused with “feature disabled” and purchase orders cannot carry lines tied to a work order. Off by default for existing and new tenants.
Screens, documents and reports affected
Subcontract receipts menu, subcontract panel on the work order, subcontract fields on the routing step, purchase order lines.
Caveats
Once off, you cannot create new subcontract POs or send material out, a routing step cannot be newly marked as subcontracted, and new work orders do that step in-house. Work already at partners can still be finished from the work order: receive the goods, bring material back, void a receipt. A subcontracted step can only be completed by a subcontract receipt, never from the generic operation status.
Example
Parts are sent to a plating shop: PO for the plating service, send 1,000 parts, the receipt for 990 plated parts consumes them at the partner and charges the fee to the order.