This step is automatic. It takes the units that came in and creates one Repair Task for each of them, then finishes.
It appears in the Add Step list as Repair Router (new).
| Automatic? | Yes - it runs and finishes on its own |
| Who does it | Nobody. It splits the work up automatically |
| Needs first | The units to repair, normally published by a Local Receipt step before it |
| Produces | One Repair Task per physical unit, each told exactly which unit it owns |
| Where you work it | Nothing to open - you see the tasks it created on the work order |
What it does
A repair job that receives five units is five separate repairs. Somebody has to bench each one, record what it needed, and reach its own outcome. This step is what turns five units received into five tasks to work.
It fans out per physical unit, not per product. Three of the same battery is three tasks, and each one is pinned to its own unit - the serial where the product has one - so two repairers never end up working the same item.
It reads those units from a published field, which means the connection is visible on the work order's Fields tab and can be re-wired. It does not go rummaging in the receipt step's private notes.
Completing it
- It completes as soon as it has created the tasks. The tasks themselves then sit in the next slot.
- If it has no units to route it refuses rather than guessing. That is deliberate: silently routing nothing looks identical to routing correctly.
When not to use it
- You already know it is one unit. Add a Repair Task directly and pin the unit on it. A router that fans out to one is just an extra row.
- You want the same work done once for a whole batch - routing gives you a task per unit, which is the opposite.