Who this page is for
If you have ASSEMBLY permission for one or more assembly areas, My Assembly Tasks is your queue. It lists every active Assembly Task step you're eligible to process — tasks already in flight at your area, plus unassigned ones that have been routed there.
Open it from the dashboard or /login/wo/myAssemblyTasks.xhtml.
The header reads My Assembly Tasks.
What's in the table
One row per active assembly-task step. Columns:
| Column | Meaning |
|---|---|
| WO # | The work order number this assembly belongs to. Production WOs typically have one Assembly Task per finished product. |
| Due | The WO's target date. |
| Product | The finished product being assembled — the target of the BOM, not the components. |
| Progress | How many units have been completed out of how many were ordered (e.g. 3 / 10). Updated live as you click Assemble 1 Unit in the processing view. |
| Shortages | A red chip if any BOM components are short of stock (BACKORDER or AWAITING_DELIVERY). Clear / empty when everything you need is at the bench. |
| Sub-asm | Count of sub-assembly tasks this row has spawned. Components that have their own BOM and an assembly area become their own Assembly Tasks; this column tells you how many are out for build. |
| Assigned To | Whose name is on the row. Empty if unassigned. |
How tasks land here
When an Assembly Task is added to a WO and the WO is released:
- The handler's
onStart()looks at the BOM, snapshots it, and works out what's available at your area now (what'sREADY/PICKED) versus what needs to come in. - For shortages it spawns Delivery Requests (warehouse pickers will bring the parts) and, where the missing component is itself assemblable, a child Assembly Task for that area.
- The parent Assembly Task lands in the assembly area's queue. Anyone with ASSEMBLY permission for that area sees the row.
Switching the area mid-WO (via WO admin's Reassign Area action on processWorkOrder.xhtml) moves the row out of the old area's queue and into the new one's.
Working through a task
Clicking the row opens the assembly processing view. From there you:
- See a live BOM table — components, required quantity, what's at the bench, what's short.
- Switch a loaded alternative if a primary component is out of stock and you have a stocked alternative configured.
- Switch a loaded conversion source mid-WO if you need to draw from a different intermediate (a different sheet, a different cable bundle).
- Click Assemble 1 Unit when everything for one finished unit is in place. The system consumes the listed components from your area and increments the completed units counter.
- Repeat until the target quantity is reached — the step then auto-completes.
Shortages and BOM staleness
Two things will pause your bench:
- Stock shortage — a delivery request is on the way; you wait for the warehouse picker. The shortage chip on this page tells you it's still outstanding.
- BOM stale — somebody changed the BOM (added/removed a component, edited a quantity, edited an alternative's consumption) since this WO was released. The processing view refuses to assemble and shows a warning banner — the production manager has to cancel and recreate the WO so it captures the new BOM.
Loaded-alternative and loaded-source pointer changes (which sheet/cable is currently being drawn from) are intentionally not stale-triggers — operators can flip those mid-WO without touching the WO header.
Tips
- The Progress column is your single best signal of what's flowing — a row that hasn't moved all morning probably has either a shortage or a stale-BOM warning.
- Sub-assembly count > 0 means parts of this build are happening at other benches. Their progress feeds into yours when they deliver.
- For component swaps (alternative or source), use the in-page controls — never hand-edit BOM rows in the catalogue while a WO is in flight, that's exactly the trigger for stale-BOM.