This article describes how previously confirmed steps in the Assistant can be reworked in order to correct errors, for example.
In addition, already completed steps can be reworked if circumstances change—for instance, when a step initially marked as MOK can later be reclassified as OK. The Rework function is used directly within the ELAM Assistant and is displayed transparently in the ELAM Analytics.
If the operator detects a faulty part during a step, the step can be confirmed with MOK, and the defect documented via the comment function. The variant is then processed further as usual. Once a new part is installed at a later point, the corresponding step can be repeated using the Rework function. In this way, the entire process remains fully documented.
To rework a step in an ongoing process, the progress bar must be opened. The progress bar shows all previously completed steps, the current step, and the upcoming steps up to the next branching point in the flowchart.
A previously confirmed step can be repeated as follows:
A copy of the selected step is generated, which can be edited. It is inserted before the currently active step, which will then be deactivated. Data recorded in the previously active step are stored and reused when the step is reactivated.
Even steps completed at another station can be reworked.
In the product history, repeated steps are marked with a "Rework" status. The repeated copy is displayed like any other step.
Will tightening data be deleted if I use the Rework function to repeat another step while in the middle of an active step?
Will I be able to identify when a step was reworked and what data existed prior to that?
