Steps in the screenshots correspond to the numbers in the headings.
This Sub-type is used when the downtime on the machine is caused by blatant customer error – ATS should not take the “hit” for the downtime.
It can be used on both CM Tasks (Correct Maintenance, MRCT - Reactive Work Orders) and EV Tasks (MOTH - Other, Event Tasks that are unplanned). This Sub-type would NOT be used on Proactive Tasks
You want to use this code sparingly: Are the PMs up to date on the machine? If not, would the machine have broken down if they were?
Is it obvious human error on the operator's part? Examples might be spilling a drink onto the panel, or taking off a glove and leaving it on the belt that jams the machine.
In this example, the customer put in the Work Order because the conveyor is not working properly. Upon investigating, the Tech found that the reason for the downtime was that the operator's jacket was caught in the belt, jamming the machine -- so he chose to mark this as NADT.
1. In the Work Module, to mark a Task as NADT, you must first find the task and highlight the row to load the screen.
2. Go to the Task Summary screen.
3. Click Edit.
4. Click on the Task Activity Sub-type drop-down arrow.
5. Choose NADT from the list.
6. Click Save.
NADT will show in the sub-types in the summary screen and in the reporting. In this case the tech also put in the description why it was NADT -- you could also do this as a note.
0 Comments
Add your comment