Previous | Next | Contents | Index | Glossary | Library |
The options available are as follows:
The system views assemblies moved into the Reject intraoperation step from the Queue or Run intraoperation step of the same operation as complete at that operation and updates operation completion information, backflushes pull components, and charges resource costs and overheads accordingly.
You can now perform the rework. When rework is complete you can move the repaired assemblies to the Queue, Run, or To move intraoperation step of the next operation.
If you do not want to rework defective assemblies at their present operation, you can alternatively move them to the Reject intraoperation step of a prior operation. This avoids recreating an operation completion (Queue or Run to Reject and Queue, Run, or To Move to the next operation) at the current operation.
If necessary, you can move irreparable assemblies into the Scrap intraoperation step of the current operation. Moves from the Reject to the Scrap intraoperation step, do not complete assemblies since rejected assemblies are already considered complete. See: Intraoperation Steps.
Rework operations should be set to count point off/autocharge off so that when good assemblies bypass them, the system does not automatically transact operation completions for these operations. In other words, you only need to move assemblies into these operations if they require rework.
Once you determine the proper rework steps for these assemblies, you can define a non-standard discrete and add the operations and components required for the rework. You can also create a rework routing that specifically addresses this type of rework. See: Rework Assemblies.
Previous | Next | Contents | Index | Glossary | Library |