Opportunity Based Maintenance(OBM)
Routine / Opportunity Based Maintenance as the name stands for, is the type of maintenance carried out to restore the technical objects to its operating condition whenever there is an opportunity or during the routine maintenance. The process effectively addresses handling the maintenance requests or the abnormalities observed in any technical object, reported by the Operations.
The process addresses the Maintenance request from user units / departments, requisitioning for some facilities, changes to be accomplished in the technical objects etc.
The process is also used for recording some work, which may not necessarily be a breakdown but some kind of modification or any other maintenance activity done by maintenance themselves, which is worth to be recorded for future reference.<./p>
Maintenance request is a targeted instruction to the maintenance department to perform an activity in the manner requested.
The decisive factor in this case is that there is no breakdown but abnormalities noticed in the machines, Difficulty in performing certain self / routine maintenance activities, to implement new ideas in the machine for performance improvement can be communicated to maintenance departments to plan their tasks and material requirement.
Maintenance requests are also used for requirement of any services in the buildings / colony like carpentry, painting, a telephone connection, provision of airline for a electronic gauge, fabrication of a stand for inspection etc. and also any services request to respective departments.
On the whole, this maintenance request can be used for making out a request for any type of requirement from maintenance department, which may be mostly in
I Proactive in avoiding malfunction or to improve production / maintainability condition.
II To register an abnormality against a technical object which can be scheduled to a later date after considering the availability of resources Reporting / Recording Activities performed.
This process can be used to record a maintenance or service activity already performed. It provides technical documentation of which activities were performed when and with what results. Countermeasures taken for breakdowns through improvements or any other modifications done in the technical object for reliability and maintainability can be recorded.
This process is therefore used for the technical confirmation of maintenance or service activities. This can be used to record any activity carried out on our own, which needs to be captured as part of technical object history.
This can include correction activity, improvement activity or any activity worth updating in database for future reference.
The following are the elements of Routine Notification along with the brief description of each tab.
Short text of the Notification carries the problem statement in brief. Long text could be used for details.
Details of the technical object would be captured in Equipment / Functional location.
Name of the person who reports the problem.
Type of abnormality / MUDA, if applicable.
The start time with date and end time with date for breakdown for any technical object is to be entered.
Required Start & End time can be used by the person who generates the Notification as intimation to the maintenance department.
Entering Catalog Details
In the notification Catalog details, you enter and maintain data describing in greater detail, the problem that occurred in an object part, damage happened to the technical object, cause that triggered the damage to the part or the activity that was performed in a technical object. This will help in analyzing the problems.
I - Plants, where Production and Maintenance department are separate entities, the request for maintenance to the maintenance department will be through the maintenance notification (Routine/Opportunity Based Maintenance [OBM] type – N1).
II-To describe the abnormalities observed in an object..
III-Document the work that has been performed along with its technical history.
IV-To book the components/ services required to rectify the abnormality.
V-To capture the cost incurred to restore / modify the technical object.
Your feedback is important to us. Please mail your suggestions/issues to amit@Erpbizz.com.
©2006-2014 ERPbizz.com. All rights reserved.
product names used or published in ERPbizz.com are trademarks of their respective companies. ERPbizz.COM, is not affiliated with any company.
This is Purely Knowledge Sharing Platform Hence Readers are requested to test all scenarios before implementation in live server.