SAP Material Links

Monday, August 25, 2014

SAP Preventive Maintenance Flow

SAP Preventive Maintenance Flow

Preventive Maintenance plays important role in smooth operation of equipment
thus it has direct impact on Production and Profitability of Organization.

Basic flow of Maintenance Cycle Shown below with Safety work permit and Goods issue against Equipment.


Monday, August 4, 2014

MTBR,MTBF and MTTR Concept and Calculation

MTBF and MTTR Concept and Calculation

By using the breakdown statistics you can analyze the causes of a particular breakdown more closely. The focus in this case is on the distribution of duration of the various breakdowns or repairs, and on how these were caused. The aim of these analyses is to find out the cause behind a short or long breakdown period, or the period between two consecutive breakdowns. An indicator in the first screen of the notification indicates that a malfunction report or a maintenance request contains a machine breakdown.
Key Figures for Machine Breakdowns
We distinguish between the following:
  • Number of machine breakdowns reported
  • Number of actual machine breakdowns
The reported breakdowns are important from a business point of view, whereas the actual breakdowns are of interest from a technical viewpoint.
There are three cases which are important for the breakdown analysis. These are represented in the following diagram, which displays two reported breakdowns in each case.

Key Figures for Downtime
The key figures for downtime comprise the following figures:
  • Downtime entered/Time To Repair
  • Mean Time To Repair
The average duration of a machine breakdown, MTTR (Mean Time To Repair), is calculated from the individual history of a piece of equipment. This gives us the following formula:

The key figure MTTR is calculated in hours.

First breakdown 10 hours
Second breakdown 05 hours
Number of breakdowns 02
MTTR = 10 + 5 / 2 = 7.5 hours

To calculate the key figure Mean Time To Repair, in the breakdown analysis (information structure S070) the effective breakdowns and the number of effective breakdowns are taken into account. In all other analyses (and the underlying information structures) the noted breakdown duration and the number of noted breakdowns are taken into account.
Key Figures for Duration Between Machine Breakdowns
The key figures for the duration between machine breakdowns comprise the following ratios:
  • Time Between Repair
  • Average Time Between Repair
The average duration between two machine breakdowns, MTBR for short (Average Time between Repair), is calculated from the individual history of the equipment. This gives the following formula:

The key figure MTBR is calculated in hours.
The following example shows how the MTBR is calculated:

Acquisition date of pump A 01/01/94
First breakdown 01/10/94
Downtime 10 hours
Second breakdown 01/20/94
Downtime 5 hours
Number of breakdowns 2
MTBR = (19 * 24 - 10) / 2 or X + Y (St) / 2
= (456 - 10) / 2 or (216 + 240 - 10) / 2
= 223 hours

When calculating the key figure Mean Time between Repair, only the start-up date can be taken into account if the indicator Start-up was set in the master data for equipment or functional locations. If the indicator was not set then the end date of the first malfunction message will be taken into account. In this case, the first malfunction message will not be used when calculating the key figure MTBR (refer to the following illustration).


Friday, April 25, 2014

SAP Quiz Links

Please check below link for SAP Quiz.


Monday, February 17, 2014

SAP Degree of Processing on Gantt Chart

SAP PS Degree of Processing on Gantt Chart

While creating the activities we have to give the normal duration, Work center and calculation key as 2 must be selected as shown below:

The project builder view will be as below

Gantt chart before confirmation:

     To view the % of processing in the chart, click on
button and in planning board select Date bar text tab and maintain fields as below.

Save the settings.
Confirm Activities as per your requirement
The following screen will appear where we have to fill processing percentage of work or actual hours of work.

Your Gantt Chart will represent the value as shown below:


Thursday, May 2, 2013

PR/PO Release Strategy re determine / Retrigger

Need of PR/PO release re determine depend on business requirement of individual companies.

 Suppose there are 2 level strategy assigned to Purchase Group

Level                   Value                       Pur Grup

A1                   0 – 1000 INR                P30              

A2                   > 10000 INR                  P30

 Buyer has created PO with value 600 Rs and got fully released now buyer wish to change PO price ideally it should go to approval again.

Here if the PO value crosses the band of 0-1000 INR it would surely go to re release
In some cases it is assumed that buyer already got approval for 1000 INR   while he has used only 600 INR out of it, so there is no need to re approval.

This setting can be achieved for both indicator i.e. Blocked or Released.

For indicator 3- release strategy would be re determine if there will be new release strategy, all value addition or subtraction changes would have no effect on existing release strategy.
 For indicator 6 – If there is change in value or new strategy or output taken system would re determine or cancel all release level in existing release strategy it self.
rest all indicators can be used as per purpose.


Blog Archive