Breakdown down MTTR Time Calculation

[gaurav_solanki2]

Hi Experts

1)        Some of the equipment always used for production during the day time example 9:00 AM to 5:30 PM.Suppose if the equipment has breakdown at 14:00 PM and maintenance team start the work on this equipment next day from 9:00 AM and he take 3 hrs for close it. Now according to user the downtime must be 6.30 hr (office Time till 5.30 + 3 hr ) while system calculate according to malfunction date and malfunction end.

2)          If an equipment is in breakdown condition from last 8 months( from July) due to some reason.This equipment also have the MTTR and MTBR records. After 8 months user close this issue , due to long time breakdown condition MTTR will Show Many Hrs and that is ok . How we can Calculate for the same Machine into August or Sep  MTTR where Still we didn't Close Notification but we want to Calculate the same into MTTR Calculation without Closing Notification .

Thanks

Rgds

Gaurav Solanki

[former_member196951]

• you can use Notification Task Tab & fields to record such interval breakdown timings like 14.00 to 15.00, 16.00 to 17.30 and so on.
• TAB name & field name to be changed if reqd.
• based on this period, MTTR/MTBR can be calculated in the custom report..
• sample snapshots are attached herewith.
• you should also take provision to upload Target data also to compare with resulted values.

[mech_vishal16]

Hi Parveen,

How to get your first attachment in SAP?

[jogeswararao_kavala]

Hello Gaurav,

Do you want to have further discussions on this topic?

Regard

KJogeswaraRao

[gaurav_solanki2]

Hi Rao Sir,

If you have any more suggestion you can share...Its also pending still due to some reasons

Regards

Gaurav Solanki

[jogeswararao_kavala]

Members will be able to reply only if you ask further. Your turn to continue.

[gaurav_solanki2]

What are the parameters we have to take and from which table to create the customizing report for my first question.

Regards
Gaurav Solanki

[jogeswararao_kavala]

• First of all small correction. It is Custom report not Customizing report .
• There will not be special tables for custom reports like this one.
• QMEL / VIQMEL is the main table you have to make use of.
• The related info structure S070 also can not help you.
  
• You can not look towards system calculate MTTR/MTBR figures for your special requirements.
• You need to calculate on your own as per your Rules in a Z-program.
• For this you have to use standard fields Malfuction Start / End Dates and Times, but need to exclude the timing you do not want to be considered in these calculations.
• For this you and the ABAPer have to work together and devise a method.
• One example can be on every such equipment you create a measuring point (can be counter too) which reads IDLE TIME.
• So your calculation during a breakdown will exclude this duration.
• You can have such many ideas.

Best of Luck

KJogeswaraRao

[Former Member]

Hi Gurav,

I suggest you or your ABAPer to have a look at logical data base AFI (trn. SE36). There you have predefined structures for all maintenance objetcs: orders, notifications, sub-orders, operations, and so on, that will facilitate the development of your report.

Regards,

mr.

[jogeswararao_kavala]

Manuel

• How do you address the duration exemptions like equipment idle times?
• Here I do not think any  need for a Logical Data Base.
• LDBs are not conventional for ABAP coding.

[Former Member]

Hi Jogeswara,

LDBs are just another tool to simplify report programming in some situations. A standard tool that's also used in some standard reports, and it's available for all to be used in z-reports.

My suggestion goes in the line of your above response: develop a z-report to extract the orders information (here enters LDBs, or not, is just an alternative) and manually calculate MTTR/MTBR based on the rules specified. In fact, here we develop a z-report for general maintenance indicators (including MTTR/MTBR) extracting the information using AFI LDB.

Regards,

mr.

[jogeswararao_kavala]

If at all LDB is useful here it should be NOTIFICATIONS, but LDB is not useful here. There is no need to go into Order area (AFI). I hope you read the initial post well. Mention and discussing about LDB is totally diverting the original requirement. Please reply to the points raised in the initial post.

[Former Member]

Hi Jogeswara,

I agree we are diverting, i don´t agree LDB are not usefull for the original requirement. Just opinions...

Regards,

mr.

[jogeswararao_kavala]

Good,

Let the author chose the right path with the available information.

[jogeswararao_kavala]

Hello Gaurav,

Your query looks very simple for me to answer because

• These calculations depend upon the company policies about what to and what not to include in the downtime.
• So, MTTR and MTBR figures will be according to your wish what you want to see with sole purpose of assessing and analysing the real performance of a machine and not for calculating unreasonably.
• So the answers to your queries largely are with you only.
• You might have already gone through these two posts:

     MTTR, MTBR, Failure Rate, Availability and Reliability

     Equipment Availability - Concept & Issues

Regards

KJogeswaraRao

[gaurav_solanki2]

Hi Rao Sir,

I have already seen these posts and the concepts is clear.But in system how we can achieve it.As my requirement is there any standard method or we have to create customize report.

Thanks

Regards

Gaurav Solanki

[jogeswararao_kavala]

• You can not achieve through standard reports.
• You have to develop a report calculate from scratch BY INCORPORATING ALL YOUR LOCAL CONDITIONS through several If, elseif etc etc.
• Pure technical. You will prepare Functional specifications according to your company policies of exclusions / inclusions and explain to your ABAPer who will develop a report to give you these MTTR figures according to your specifications.
• If you query about what should be the policy, I'm afraid this is not the forum. That query will go to some forum such as IMS.(ISO9000 etc)