MTTR and MTBR fields are calculated by work order. User has to report downtime on the asset. MTTR/MTBR fields will never display if downtime on an asset is not reported. I did not see any MTTR/MTBR reports from OOB. We created a package that calculates the rollup throught Asset Utilities. Here is a breakdown you can do manually.
For the example below we will use Siteid = BEDFORD and Asset # G1283
Mean Time To Repair (MTTR) formula is (Total Production Downtime) divided by (Number of Breakdowns)
The MTTR will be a decimal number for example: 96.05, which depicts 96 hours and 3 mins. Because the code in this program requires 2-point decimal presentation, what you will do is divide 3 into 60 you get .05. To double-check your calculation compute .05 of an hour (60X.05) you get 3, which perfectly correlated with the minutes in the YTD Downtime field.
Example:
On 03/04/2020 the equipment went down at 6:32 pm (1832 military time) and you need to subtract this from 24 hours. It is easiest to let SQL do that calculation for you. The select for that is:
SELECT (to_date('02/21/2020 07:10:00','MM/DD/YYYY HH24:MI:SS') - to_date('02/20/2020 16:24:49','MM/DD/YYYY HH24:MI:SS')) * 24 FROM DUAL
Your most recent date goes first, the oldest date goes second. For this we are just looking to see how many hours the asset was down on March 4th.
The first date in the select will be Mar 5th at midnight. Midnight will be displayed as 00:00:01 which is actually 1 minute after midnight, but that is the only way we can get SQL to calculate it.
The 2nd date will be Mar 4th with the time it went down expressed in a 24 hour clock time.
The select gives us 5.457 hours of downtime. Converting the .457 to minutes would be 5:27 (rounding does play a part here. I'm not too concerned if we are off by a minute, but much over that, gives cause for concern.)
From the 5th – 6th of Mar the system was down for 48 hours, so the math would be 24 hours X 2 days = 48 hours
48:00 hours + 5(hours):27 (mins) = 53:27
Now you need to calculate for the rest of March. Based on the calendar, there are 17 days left that the asset is supposed to be up for 24 hours each day. 24:00 x 17 = 408 hours.
Total downtime for March is 461:27 hours.
The total downtime for April = 22 x 24 = 528 hours
The total downtime for May = 20 x 24 = 480 hours
The total downtime for June = 22 x 24 = 528 hours
We have to calculate the downtime for July just like we did for March. The first date in the select statement will be 07/20/2020 07:39:00 and the 2nd date will be 07/01/2020 00:00:01. That gives us 463.64972 or 463:39
Then we actually have another 'break' in July for 1 minute. Since it is just a minute, we will actually just add it in. If it was longer and we needed to calculate using TOAD we would. But your Total downtime for July is 463:40
Total Downtime for the entire period for this asset is for all months added together = 2293:07, converted to tenths of an hour, 2293.116
The last number we need is the Total Production time. This is found by looking at the calendar for the asset for the month in question. For this example, the EQQ54-C for July 2020, shows 22 days for 24 hours on those days. So Total Production time = 22 x 24:00 = 528.
Now you have the values you need to calculate both MTBF and MTTR for the asset.
· Calculate Mean Time Between Failure and record in the Record Event column.
MTBF: (Total Production time – Total Downtime)/# of Breaks
Total Production time = 528 (for each month)
Total Downtime = ea month
# of Breaks = each month
Mar - (528 – 461.27)/1 = 66.73
Apr – (528 – 528)/1 = 0.0
May – (528 – 528)/1 = 0.0
Jun – (528 – 528)/1 = 0.0
Jul – (528 – 463.40)/2 = 32.3
· Calculate Mean Time To Restore and record in the Record Event column.
MTTR: Total Downtime/# of Breakdowns
Total Downtime = 2293.116
# of Breaks = 2 (asset came up twice in the month of July)
2293.116/2 = 1146.558 or 1146.01
Hope this helps!
A.S. Bearden
------------------------------
A.S. Bearden, GDIT
'ADAM'
------------------------------
Original Message:
Sent: 01-24-2024 10:16
From: ken trotta
Subject: Reports for Mean Time to Repair (MTTR) and Mean Time Between Repairs (MTBR)?
Hello,
I'm new to Maximo and this forum. Are there basic reports available for MTTR and MTBR?
Maintenance closes about 50 corrective repairs a month. Service Request dates are somehow separate from the Work Order closure date.
Any help is appreciated!
#EndUser
------------------------------
Ken Trotta
Sequoia Consulting Group
------------------------------