These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Mining ERP
- Features
- Processing
Processing
Release bounded assembly and repacking work, then reconcile output cost.
OverviewProcessing schedule×
Mining ERP · Processing
New
Processing schedule
Work orders
| Work order number | Status | Planned start | Planned end | Output material | Manager | |
|---|---|---|---|---|---|---|
| WO-76751 | Released | 20 Oct | 27 Oct | Crushed basalt, 3/4 in | Luca Ferri | |
| WO-17244 | In progress | 14 Oct | 20 Oct | Iron ore fines, 62% grade | Mei Lin | |
| WO-26907 | Partially completed | 04 Oct | 06 Oct | Silica sand, dry bulk | Tariq Hassan | |
| WO-31560 | Released | 18 Oct | 20 Oct | Crushed basalt, 3/4 in | Tariq Hassan | |
| WO-78283 | In progress | 05 Oct | 07 Oct | Crushed basalt, 3/4 in | Tariq Hassan |
6 of 6 records
Crushed basalt, 3/4 inWork orders · WO-76751
ReleasedPlanned start20 Oct
Planned end27 Oct
ManagerLuca Ferri
What you can do
Freeze the work instruction
A work order uses an active bill of materials and routing for a named output material. The planned quantity, output basis, standard cost and stockpile establish its release scope. Warehouse Manager checks these facts and the assigned operations before approving release. Material needs become reservations; issuing input material is a stock event with an associated cost entry.
How the work is organized
- Source. Freeze the active recipe, routing and output basis before work release.
- Decision. Warehouse Manager approves the planned quantity and standard cost.
- Evidence. Warehouse Operator records issued input, operation progress and terminal accepted output as separate events.
Warehouse Operator records actual operation throughput, scrap and labor hours. An intermediate operation is progress evidence, while a terminal completion establishes accepted output. Processing Completions allocate actual work-in-progress cost to finished quantity and show standard output value and variance. The close decision reviews residual variance rather than simply changing a label.
What to agree during setup
Agree how input units convert to output units, which operation completes the routing and who reviews residual cost variance. Review the roles that can prepare, approve and correct the record. Keep the source revision and its later decisions linked for audit.
Check the handoff on an actual case
For a repacking run, rehearse a partial output from an input lot. Verify required, issued, returned and consumed material separately. Record an operation entry and only the accepted terminal output as finished stock. Compare the output value with accumulated cost and retain the variance for Finance Manager review.
Repack a partial lot and compare issued, consumed and returned material with accepted terminal output before closing the work order. Ask the receiving role to open the source and confirm the remaining quantity, decision and event date. Preserve a linked correction if an earlier event needs to be amended.
Agree the handling of scrap and returned input before releasing work. A stopped operation still retains the material issued and labor evidence already recorded. The completion review compares actual input and output to the frozen instruction, with any difference carried into the cost discussion.
What your team sees
- Processing schedule — Show released and active work with planned start and end dates.
- Stockpile availability — Show material available for an approved input reservation.
Follow the work through
Read the main flow and the connected handoff.
What it keeps track of
Data model- BOMs
- Effective distribution assembly/repacking recipes with explicit output basis.
- BOM lines
- Component quantities per explicit output basis, preserving dimensions and allowed loss.
- Processing routings
- Versioned assembly/repacking instructions, distinct from delivery routes.
- Processing operations
- Ordered work instructions and declared labour/overhead bases.
- Work orders
- Released bounded assembly/kitting/repacking, without plant APS or payroll scope.
- Work order materials
- Frozen required input and actual traced issue/return scope.
- Work order operations
- Frozen instructions and assigned actual work.
- Processing entries
- Actual operation throughput, scrap and labour evidence; intermediate counts do not sum to output.
- Processing completions
- Accepted terminal output and WIP cost allocation, once per actual completed scope.
- Work order cost entries
- Immutable WIP debit/credit sources and bounded actual-cost allocation.
- Stockpile reservations
- Exclusive bounded demand claims through picking and owned transit.
Who uses it
Permissions- Warehouse Manager
- Releases work and reviews completion.
- Warehouse Operator
- Records operation evidence.
- Finance Manager
- Reviews cost and variance.
Set up Mining ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.