Essential Resources: To complete this training you must have access to eFACTORYPRO.
1. With your supervisor credentials, log into the Work Module.
Click on Review from the Work section of the Navigation Pane.
2. From the drop-down, you can choose either Completed Tasks or Canceled Tasks.
The default view is Completed Tasks.
3. Highlight the line of the Task you want to review.
4. The bottom panel will load on the Task view.
Everyone has their own way of reviewing. You can either go to the summary panel and scroll down to review all the way down, or you can go through the badges and review anything that has a quantity higher than one.
Scenario 1: All the required information has not been completed. In this case, the first thing that stands out is that parts is red.
This indicates that not all the parts have been consumed.
This should NOT normally happen... the system stops you from completing a task when all parts have not been consumed. However, it is possible that occasionally the system could "glitch" and you could see something like this.
When you see it, it must be fixed.
As the Supervisor, if you don't know whether the remaining part needs to be consumed or canceled you should send the Task back to the Technician by following the steps below.
2. A pop-up box comes up.
3. Enter a comment as to why you are reopening the task.
4. Click YES.
A confirmation message tells you that the Task and WO have been successfully reopened.
One of the things that deserves extra attention whenever you see it is a Malfunction badge with a number after it. Because of the huge impact this can have on your metrics, it is very important that you review ALL malfunctions!
Some things you should be looking for include:
- Breakdown = Yes happens when the downtime starts within a minute after Task creation or any time before.
- If this is incorrect, and the task should not be a breakdown, you must remove the Breakdown = Yes.
- You need to delete or edit the malfunction until the proper time is shown.
- If you do not remove the Breakdown flag (Breakdown = Yes), then your MBTF and MTTR will be skewed in the wrong direction.
An overlapping malfunction will mean you are charged for "double" downtime for the time displayed.
The screenshot below shows a different example than the one above.
It is important to review the length of the malfunction in comparison to dates and times of Task and labor entries
Although Malfunctions are most commonly found on Reactive Work orders, it is possible to find them on other types of work as well.
In our example below, we are reviewing a CM Task where we were asked to fix a problem with the power supply on a machine.
The Task was created on July 20th, just after 8:30 AM
You can see there are entries on Steps, labor notes, parts repair and malfunction.
1. It is important to review the length of the malfunction in comparison to dates and times of Task and labor entries
2. When looking at labor, you can see that our Technician worked on this a little more than a half hour, finishing just after 9:30 am -- about an hour after the Task was created.
4. Therefore, it's obvious that there might be a problem with the malfunction time when we click on that Tab.
5. The start time is 8:34 - the time of work order creation.
6. The stop time for the malfunction is three hours and fifteen minutes later - when in actuality, the work was finished in less than an hour from the breakdown.
Several things could have happened to get us to that point, so you will definitely need to do some research.
7. If the malfunction is incorrect and needs to be edited, you can click on the three dots under the action menu and click edit.
You do not have to reopen the Task to make the changes.
8. If the malfunction should not be there at all, you can simply delete it by clicking on the three lines and choosing Delete from the action menu.
You will be asked to confirm your actions.
There is no event that tracks the deleting of the malfunction so be sure that is what you want to do before clicking yes.
In this case we shouldn't delete the malfunction, we had to edit it as shown in the screenshots above.
0 Comments
Add your comment