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.
- Kitting & Assembly
- Features
- Assembly execution
Assembly execution
A released kit build gives operators an ordered set of work instructions. Each work order operation carries the selected routing operation, planned dates and assigned person. Its own status shows whether it is ready, in progress, complete or in exception. Actual start and end times capture what happened on the floor rather than rewriting the plan.
OverviewOperations assigned to me×
Kitting & Assembly · Assembly execution
New
Operations assigned to me
Work order operations
| Kit build | Routing operation | Status | Planned start | Planned end | Assigned to | |
|---|---|---|---|---|---|---|
| KB-35342 | RO-7863 | Ready | 25 Oct | 01 Nov | ||
| KB-82807 | RO-3355 | In progress | 10 Oct | 17 Oct | ||
| KB-12048 | RO-1179 | Complete | 25 Oct | 02 Nov | ||
| KB-65242 | RO-5282 | Exception | 03 Oct | 08 Oct | ||
| KB-76486 | RO-2584 | Ready | 15 Oct | 18 Oct |
6 of 6 records
KB-35342Work order operations · WOO-76202
ReadyRouting operationRO-7863
Planned start25 Oct
Planned end01 Nov
What you can do
Record the work as it happens
Warehouse Operator records a production entry against the operation. The entry captures start and end, good quantity, scrap quantity and labour hours. It begins as a draft and can be submitted for review. Warehouse Manager compares the reported quantities with the operation and the build’s released scope before accepting the entry. A correction retains its link to the earlier record.
Suppose a team starts a run of display kits and damages a small quantity of sleeves. The entry should show good kits and scrapped pieces separately, with the actual labour time. The build’s final output is not the sum of every intermediate operation’s good quantity. A terminal operation and accepted completion define finished output. This prevents a pack assembled, labeled and checked at successive steps from appearing as finished stock several times.
How the work is organized
- Instructions. The frozen routing operations give an ordered name, instruction and terminal marker for the build.
- Assignment. Work order operations connect those instructions to an assigned person, dates and actual execution state.
- Evidence. Production entries retain measured good output, scrap and labour with a reviewer and correction lineage.
What to agree during setup
Walk the real floor sequence and decide which operation creates the completed kit quantity. Confirm what staff should record as scrap at each point. Agree how a partly completed build is reported and how a stopped operation moves into exception. Make sure the person assigned to an operation can identify the correct build and instruction without relying on a verbal job name.
The manager should review a sample entry that spans a shift boundary and one with scrap. Labour hours, start and end times need to describe the same actual work. Where instructions change, issue a new route version for future work and keep the released build on its existing basis. The team can then explain why two batches used different work steps.
Check the handoff on an actual case
Take a released build with an assembly step and a terminal packing step. Assign each operation to a named operator. Record the first step with good units, scrap and labour hours, then submit it. Have Warehouse Manager accept the evidence before the next step uses that quantity. Record the terminal step for only the units that reached finished condition. If a quantity was entered against the wrong operation, use a linked correction and verify that the original history is still visible.
What your team sees
- Operations assigned to me — Current operator assignments with their planned times and state.
- Production entries for review — Submitted throughput and labour that a manager must check.
- Build status board — Active builds and those waiting for completion or close.
Follow the work through
What it keeps track of
Data model- Work order operations
- Frozen instructions and assigned actual work.
- Routing operations
- Ordered work instructions and declared labour/overhead bases.
- Production entries
- Actual operation throughput, scrap and labour evidence; intermediate counts do not sum to output.
- Kit builds
- Released bounded assembly/kitting/repacking, without plant APS or payroll scope.
- Work order materials
- Frozen required input and actual traced issue/return scope.
- Review decisions
- Authoritative human decisions independent of document lifecycle.
Who uses it
Permissions- Warehouse Operator
- Records the assigned operation and actual quantities.
- Warehouse Manager
- Reviews entries, exceptions and the route used for the build.
- Finance Manager
- Reviews cost consequences when variance needs a decision.
Set up Kitting & Assembly your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.