Capturing Probable Revenue Lost & Production Delays due to breakdown
This blog provides details of a custom solution that will enable asset & production intensive industries to capture key information related to delay in production due to maintenance activities (majorly due to breakdown). This document provides details of the solution with appropriate technical references as needed. The technical specification involved with this solution are not covered in this blog.
In asset & production intensive industries such as pharmaceutical, refineries, FMCG etc. circumstances may arise where production either has to be stopped or slowed down due to breakdown or due to maintenance activities. In such cases the standard SAP process suggests us to create PM notification first and then converting it to work order for executing maintenance work. In standard maintenance notification and work order allow us to capture majority of the information related to maintenance activities carried out but information related to impact on production cannot be captured directly. For example
- for how much time production was stopped
- Any backup available or not
- Further Comments
Most importantly, the probable revenue lost is not captured anywhere.
In practical scenarios the delay in production is not always same as that of malfunction start and end time. The delay in production depends on many dynamic parameters like the current production schedule when breakdown occurred, type of production being carried out MTS/MTO. Therefore the delay in production can’t be derived directly from the standard breakdown notification. This delay in production should be calculated manually and then entered into customized notification. A custom report will read this data from such notifications and will provide the different data points.
Lets discuss the process in detail to understand the concept.
1. Business Driver
For production industry machine up/running time is very important. Lower MTBR (Mean time between the repairs) can directly impact the financials of the company.
The standard SAP PM and PP integration processes provide us functionality to capture the machine breakdown time , production schedule but doesn’t provide the flexibility to capture the key financial figures related to breakdown : Production stopped or not , Time for which production was stopped due to breakdown , Probable revenue loss due to this , Probable Sales loss due to breakdown etc.
2. Design Consideration
The custom solution will cover the data elements as listed below.
- Equipment Master
- Functional Location Master
- Production Order
- Breakdown Notification
The solution can be divided into 3 logical components.
- Custom table storing Material No and corresponding per hour Qty produced at 100% load
- Capturing the data related to breakdown and Production Stoppage
- Generating financial report
Adding data to custom table for storing material no and the per hour Qty produced will be one time activity. The information in the breakdown notification will be captured via custom fields ( Z fields) & also these fields will be appended into standard list reports like IW28/I29
3. Technical Consideration
Below are the custom fields to be added in the custom Z table :
- Material No
- Qty Produced ( Per hour)
Below are the custom fields which are required to be added in the breakdown notification:
- Production Stopped (checkbox)
- Delay in Production (Numeric field)
- Material No of the product whose production stopped ( Numeric)
- Production Capacity Load/Rate( Numeric )
Screen Exit QQMMA0001 should be used to add custom field in the notification. The custom fields should also be added to the table QMEL which stores the data related to notifications in SAP.
Clicking on components will give us the components
After adding the custom fields on notification using above exit , below configuration steps should be carried out :
- Navigate to overview of the notification node in SPRO
- Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view
To add above fields on list reports (IW28/29) we need to create an Append Structure in the Structure RIHQMEL_LIST(RQMQMEL1 in case of QM10/QM11 reports)
Once the fields custom fields are added to notification and can be saved in table QMEL then custom report can be used to read this data and further process it.
Below fields should be available on the selection screen of the report:
- Fiscal Year / Quarter
- Sale Price
Main output fields would include
- Probable Revenue loss
- Probable Standard Cost Loss
- Probable Loss of Profit
- Material No
- No. of breakdown notifications selected for calculations
- Equipment with maximum number of breakdown hours
- Qty Lost due breakdowns
- Production Halt (Total Hours)
All the breakdown notifications with the “Production Stopped indicator active” will be selected on the basis of the values entered on the selection screen.
Following calculations can be used to calculate the values for above fields
- Qty Lost due to breakdowns = (Qty Produced Per hour * Production Capacity Load/Rate * Production Stopped Hours)
NOTE: Calculate above field for each notification selected and then add the value to find Qty Lost due to breakdown per material
- Probable Revenue Loss = (Qty Lost Due to breakdown * Sale Price)
- Probable Standard Cost Loss = (Qty Lost Due to breakdown * Standard Price of the Material)
- Probable Loss of Profit = (Probable Revenue loss – Probable Standard Cost Loss)
After implementing the above process below KPIs will be available to the business:
- Comparison between Breakdown Hours and corresponding Production Delay Hours
- Above comparison leads to further availability of key figures like Probable revenue lost & Probable Profit Lost
- A report to monitor asset performance with direct financial figures
The custom report/process can be modified to suit any specific business need.