KPI for restoration speed

MTTR – (MDTR)

Mean Time To Restoration – (Mean Downtime To Restoration)

MTTR describes the time from fault detection to restoration of the machine. It may include administrative and logistics delays.
Example: during a month, the maintenance department spent one hour fixing a pump the first time, two hours the second time and three hours the last time. MTTR for this pump is two hours.

Needed Data:

Site-Object

Time for restoration
(downtime for restoration)

Number of failures

Calculation:

Relevant for:

Tracked for:

Groups
Site-objects
Departments
People

Calculation based on:

Time differences
In MaintMaster:
Configured by user

 

MTTR is a KPI which is officially recommended to measure by several Quality Management Systems e.g. IATF 16949.
It describes the mean time from a fault detection to restoration (repair, recover) of a machine or system.
To measure it correctly you need to have a clear and described routine in place for reporting the detection of a fault and completion of the repair. The clear and documented way of measure will help you a lot during audits.
In order to have a an easy way of measuring and following up MTTR it is recommended to report ALL corrective maintenance tasks in your CMMS.
In MaintMaster you are able to analyze this KPI in several dimensions: MTTR for Machines, Lines, Departments or even groups of technicians. This is helpful if you observe changes to the KPI and need to find the root cause for these changes.
As usual we recommend to concentrate not only on absolute time measures but also consider trends and developments over a time period. MaintMaster supports this by showing you the absolute number as well as trends based on historic data.

MWT

Mean Waiting Time

Mean Waiting Time describes the time it takes for a fault (not planned jobs) to be registered and maintenance technicians starting to work on the problem. In order for this KPI to be measurable, it has to be clearly defined what it means to start working on a task.
Example: A corrective maintenance task takes 8 hours to complete. It took 4 hours for the spare part to arrive until the team could start working. MWT is at least 4 hours.

Needed Data

Time of fault report

Reported times

Object / Person / Group

Calculation:

Relevant for:

Tracked for:

Site-object
People
Groups

Calculation based on:

Time differences
Reported times
In MaintMaster:
Configured by user

*Mean Time to restoration

**Reported time by several people needs to be separated

Downtime due to missing spare parts

Hours of downtime caused by missing spare parts

Describes the downtime for a machine due to lack of parts.
Example: We have a breakdown in one of our machines. It took 7 hours to get the machine up and running again. 5 of them were spent waiting for a spare part to arrive.

Needed Data

Site-object

Downtime

Time of completed restoration

(Responsible person / Group)

Needed spare part

Calculation:

Relevant for:

Tracked for

Site-objects
Spare part
Companies
Departments

Calculation based on:

Downtime
In MaintMaster:
Configured by user

 

 

 

Download the KPI Manual: