My Assembly Tasks
If you have ASSEMBLY permission for one or more assembly areas, My Assembly Tasks is your queue. It lists every active Assembly Task you are eligible to process - tasks already in flight at your area, plus unassigned ones routed there. Open it from the dashboard or /login/wo/myAssemblyTasks.xhtml.
How assembly works
An Assembly Task builds one finished product from its bill of materials (BOM), one unit at a time. When the work order is released, the task looks at the BOM, takes a snapshot of it, and works out what is already available at your area versus what is short.
- For anything short, it raises Delivery Requests so warehouse pickers bring the parts to your area - and where the missing component is itself assemblable, it spawns a child Assembly Task for that component's area.
- You then assemble unit by unit: when everything for one finished unit is in place you click Assemble, the components are consumed from your area, and the completed-units counter ticks up.
- The task does not finish itself. Even at the last unit you click Complete assembly yourself - so you can review the build and add notes before locking it.
The queue
One row per active assembly task:
| Column | Meaning |
|---|---|
| WO # | The work order this assembly belongs to. |
| Due | The WO's target date. |
| Product | The finished product being built - the target of the BOM, not the components. |
| Progress | Units completed out of units ordered (e.g. 3 / 10). Updates live as you assemble. |
| Shortages | A red chip if any BOM component is short (on backorder or awaiting delivery); clear when everything is at the bench. |
| Sub-asm | How many child sub-assembly tasks this row has spawned (components with their own BOM being built at other benches). |
| Assigned To | Whose name is on the row; empty if unassigned. |
As with repairs, area eligibility decides visibility - anyone with ASSEMBLY permission for the area sees the row, assigned or not. An admin's Reassign Area moves it between areas.
The assembly screen
Clicking a row opens the mobile-first assembly screen: a header with the finished product and a units-assembled progress indicator, then the working sections.
Materials (per unit, at the assembly area)
One material card per BOM component, showing the component's thumbnail, description and [CODE], and a need vs available readout on the right - green when you have enough per unit, red (with a shortfall like "-3 short") when you do not. This is your at-a-glance readiness check.
Serialized components. A component that is serialized gets a serial picker under its card: type or scan into Scan / pick serial..., pick from the matches, and Add - or use All (N) to grab all the serials you need from one location at once. Each chosen serial shows as a chip you can remove; a counter shows "picked / needed".
Alternatives. If a component has approved alternatives, an Alternatives list lets you Load a different product when the default is out of stock. The loaded one is marked with a star; Unload reverts to the default. Upcoming units then consume from the loaded alternative.
Sources. If a component is an intermediate product (a "kit" drawn from a larger source - a sheet, a cable bundle), a Sources list lets you Load which source to draw from. Same star / unload behaviour.
Quantity to build
A stepper (default 1) sets how many units to assemble in this batch. Raise it to build several at once when materials allow - the serial requirements update to match.
Output serials. If the finished product is itself serialized, an Output serials box asks you to enter one unique serial per unit you are building (e.g. "enter 2"). You must enter them all before you can assemble.
The action bar
A sticky bar at the bottom carries the primary action:
- Assemble N units (green) - consumes the materials for that many units, records any serials, and advances the counter. It is enabled only when you have the stock, all serialized components have the right number of serials picked, all output serials are entered, and the BOM is not stale. Assemble as many batches as you like.
- Complete assembly (appears once all ordered units are built) - marks the task done and hands off to the next WO step. You must click it - the task never auto-completes. An optional Assembly notes box lets you record observations first.
- Pause task / Resume - hold the bench (with an optional reason) and pick it back up.
Pending deliveries, shortages and history
A collapsible panel shows Pending deliveries (the delivery tasks bringing in short components, with their status), Shortages (each short component with need vs available in stores and the exact shortfall), and History (every unit built so far, with its output serial and timestamp).
Two things that stop your bench
- Stock shortage - a delivery request is on the way; you wait for the picker. The shortage chip on the queue tells you it is still outstanding.
- BOM stale - someone changed the BOM (added or removed a component, edited a quantity, edited an alternative's consumption) after this WO was released. A yellow banner appears and assembly is blocked - the snapshot no longer matches the live BOM. A production manager must cancel and recreate the WO so it captures the new recipe. (Switching a loaded alternative or a loaded source mid-build does not trigger staleness - those are legitimate operator choices - though a blue banner warns that shortages raised for the previous choice may now be stale.)
Tips
- Progress is your best signal - a row that has not moved all morning almost certainly has a shortage or a stale-BOM warning.
- Sub-asm > 0 means parts of this build are happening at other benches; their progress feeds yours when they deliver.
- For component swaps, always use the on-screen Load / Unload controls - never hand-edit BOM rows in the catalogue while a WO is in flight, because that is exactly what triggers a stale-BOM block.