It is always a good idea to stay on top of your data!!! If you update data older than 4 months, you will not see the changes until the following Monday. (It refreshes Sunday overnight.) If your data is older than 13 months, it may not be worth updating. The changes will not show up until the second day of the next month.
Steps in the screenshots correspond to the numbers in the headings.
It should be recorded as a breakdown if the machine was not running at the time of Work Order creation. It is NOT a "Breakdown" when the Technician has to take the machine down to do the repair. It is important that you understand how "Breakdown" affects your metrics, and that Technicians review the Malfunction information carefully before completing the Task to ensure it is marked correctly. It is equally as important that the Supervisor or Planner/Scheduler double check this when Reviewing and Closing the Work order.
1. Breakdown on a Corrective Maintenance Task (Reactive Work Order) indicates "Unscheduled Down Time" in terms of your metrics.
This directly feeds into the Downtime and Availability Metric that you report out to your Customer on a Monthly basis.
2. A Breakdown = a FAILURE. This means that having having a task as a breakdown will cause this Task/Work Order to affect your Mean Time Between Failure Metrics.
If the task was left as a breakdown in error, you are possibly inflating your failure count, shortening the time between failures with false data. To correct this simply delete the malfunction entry.
3. Some of our customers measure the Cost of Non-Conformance: Labor hours on Reactive Tasks with a breakdown are a key driver of this metric.
If you are a site whose customer measures this metric, when reviewing Work Orders, be sure to check for Malfunctions that show Zero Downtime, and Breakdown = yes. Correct these before closing the Work Order or all the labor hours will be going against your CONC metric.
0 Comments
Add your comment