Introduction:
The environment in which the present subject is being discussed is that, where Large Machine installations like Furnaces, Cranes etc have been mapped as Functional Locations and the Equipments hierarchy follows under them.
The author, in the past had posted a document on the subject matter Equipment Availability - Concept & Issues. As defined in this document the usual method of deriving Equipment Availability through MTBR, MTTR parameters is by the formula:
Everything was OK until we see the Equipments in isolation. It did not take longer for the Audit persons to reach the Logic that in an Enterprise Structure, if an Equipment undergoes breakdown, the Functional Location also goes inoperative. M2 Notifications are recorded on the Equipments but its effect impacts the hierarchy, finally affecting the bigger machine i.e., the Functional Location in our case.
The Audit demand was that the Equipment Availability figures be made available at the Functional Locations level, even when no direct M2 notifications are created on them.
Naturally, we approached OSS. The recommendation was in the form of implementing an SAP note namely 1074845, but with conditions like no further software support would be provided in relation to this. This is relevant to Functional Location-Equipment Hierarchy only, not to Equipment-Equipment Hierarchy. Meaning that, the MTTR, MTBR vales will be collected to Functional Locations only, but not to Superior-Ord Equipments.
Objective:
So the objective of this document is to compute Nodal Equipment Availability on Functional Locations as explained above.
Let’s see how we do it !
Readers might by now have understood that by implementing the said SAP note, SAP will be providing the collective MTTR, MTBR values on the Functional Locations. Using these values our requirement of Calculating the Availability values can be easily calculated through formula given above.
Step1 (Implement the SAP note)
Steps suggested in SAP note 1074845 were implemented by BASIS people.
Important: The nodal MTTR, MTBR computation effect in the report MCJC would be seen with a condition that atleast One M2 Notification is created directly on this Functional Location. (This was the pee-requisite SAP informed us). Also we 'd experienced this. Until no M2 Notification is created on a F/Locn, the MCJC report was coming blank inspite of several M2 Notifications exist in the hierrchy of this F/Locn. The moment we create such Notification, immediately the MCJC report starts showing the computed figures of hierarchical MTTR, MTBR values..
Step2 (Cross-check the impact of SAP note)
We manually checked the correctness of the collective values of MTTR, MTBR on the Functional Location through MCJC, by deriving from the individual Equipment values of MCJB. We confirmed that the things are accurate.
Note:
Here I want to share one information with the readers. Few might be wondering that this requirement can be well addressed by a simple development. Even I too tried this. Such development would be very complex because, taking care of Breakdown Duration Overlaps of Equipments under a Functional Location would be very complicated and so a less reliable code would be an outcome if developed locally. The same thing comes from Standard through this SAP-note in an accurate way.
Step3 (Update S070 info-structure)
While testing we realized that the info-structure S070 which computes the MTBR, MTTR values does not update instantaneously. So we developed a simple program to update S070 info-structure (Calling Tcodes OLPM and OLIX in the code) and scheduled it to run 12hourly.
Step4 (Develop a program to compute the Equipment Availability)
A simple program using table S070 (for periodical MTBR and MTTR values of the Functional Location) has been developed which calculates the Equipment Availability (in our case the Functional Location) using the formula given in the beginning.
Selection-screen
ALV Output
Note:
This is to reiterate that SAP did not give any solutions to compute similar calculations on SuperiorOrd Equipments in relation to the sub-equipments. Also, these collective computations are valid on the immediate Functional Locations above the Equipment hierarchy. So starting with the Equipments which need these collective MTTR/MTBR computations, we had to modify our structures to suit the present situation .
(Hoping that Readers will be able to distinguish the use of word Equipment in this article, sometimes it meant as an SAP object and at other it has general Equipment meaning)
...and I feel here too it is important for me to mention the version of my system where all these exercises were to be done. It is ECC6.0 no EHPs.
Hope members find this article useful.
Thank you
KJogeswaraRao