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.
- Shipbuilding ERP
- Features
- Assembly and repacking
Assembly and repacking
Release bounded assembly work against recipes, operations, issued material and cost.
OverviewMy operation assignments×
Shipbuilding ERP · Assembly and repacking
New
My operation assignments
Work order operations
| Work order | Routing operation | Planned start | Planned end | Actual start | Actual end | |
|---|---|---|---|---|---|---|
| WO-69115 | RO-2842 | 16 Oct | 22 Oct | 24 Oct | 28 Oct | |
| WO-70708 | RO-1009 | 03 Oct | 07 Oct | 10 Oct | 12 Oct | |
| WO-94999 | RO-4799 | 23 Oct | 26 Oct | 03 Nov | 06 Nov | |
| WO-49075 | RO-6168 | 22 Oct | 27 Oct | 03 Nov | 07 Nov | |
| WO-37219 | RO-8934 | 22 Oct | 29 Oct | 01 Nov | 04 Nov |
6 of 6 records
WO-69115Work order operations · WOO-84618
ReadyRouting operationRO-2842
Planned start16 Oct
Planned end22 Oct
Actual start24 Oct
Actual end28 Oct
What you can do
Start with an effective recipe
Warehouse Manager uses a bill of materials and a production routing to define a kit or repacked output. The recipe states the output basis and each component quantity. Operations name the ordered instructions, labour basis and terminal operation. Product and unit versions matter because a changed master must not recalculate an accepted work order after material is issued.
A work order names its legal entity, warehouse, output product, planned quantity, manager, effective recipe, routing and output standard. Its release is a human decision on the frozen scope. Material reservations and issues then trace each required component. Actual production entries capture throughput, scrap and labour at an operation; intermediate good counts cannot be added together as finished output.
How the work is organized
- Frozen basis. The released work order retains the recipe, routing, quantity and standard used to approve it.
- Actual work. Assigned operations record start, end, good quantity, scrap and labour evidence.
- Cost relief. Completion allocates actual WIP to accepted terminal output and records the variance separately.
What to agree during setup
Agree who owns the recipe and who independently activates changes to it. Define product-specific units, allowed planned loss, operation sequence and the output standard. Warehouse Manager decides whether material and labour evidence is sufficient to release and close a work order. Finance Manager reviews required variance or cost decisions; Accountant reconciles WIP and postings. A customer order line may be linked to the work order, but the output remains a product quantity in a warehouse, with its own stock event.
Choose how warehouse staff record issue, return and scrap. Unused issued components should be returned explicitly. A partially completed work order retains its remaining planned and material scope, rather than presenting the full planned quantity as finished stock.
Check the handoff on an actual case
Build a packaged set of stocked components for a customer order. The approved recipe specifies input quantities for a stated output basis. Release the work order only after the right output product, standard, routing and positive planned quantity are present. Reserve the material, issue only what the first run needs and record the actual operation. If some input is scrapped, retain the scrap quantity and cost evidence rather than hiding it in finished units.
Confirm a terminal completion for the accepted output. It should create stock once and relieve only the WIP assigned to that completion. Another operation entry cannot create a second finished batch from the same terminal quantity. Before closing, reconcile remaining material, output and variance; an independent decision is needed where residual variance requires one.
What your team sees
- Production schedule — Warehouse Manager sees released work and planned start and end dates.
- My operation assignments — Warehouse Operator records assigned operations and actual work.
- Warehouse availability — The team sees accepted output once it has become owned stock.
Follow the work through
What it keeps track of
Data model- BO ms
- Effective distribution assembly/repacking recipes with explicit output basis.
- BOM lines
- Component quantities per explicit output basis, preserving dimensions and allowed loss.
- Production routings
- Versioned assembly/repacking instructions, distinct from delivery routes.
- Routing operations
- Ordered work instructions and declared labour/overhead bases.
- Work orders
- Released bounded assembly/kitting/repacking, without plant APS or payroll scope.
- Work order components
- Frozen required input and actual traced issue/return scope.
- Work order operations
- Frozen instructions and assigned actual work.
- Production log
- Actual operation throughput, scrap and labour evidence; intermediate counts do not sum to output.
- Production 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.
- Inventory
- Current owned stock by complete identity and custody state; provenance is not a second balance.
- Stock events
- One immutable group of stock movements and the associated journal effect.
Who uses it
Permissions- Warehouse Manager
- Reviews release and completion.
- Warehouse Operator
- Records assigned physical work.
- Finance Manager
- Reviews standards and required variance decisions.
- Accountant
- Reconciles WIP and posted output.
Set up Shipbuilding ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.