Documents

Oracle EAM Process Flow and Business Cycle

Categories
Published
of 16
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Share
Description
Oracle EAM Process Flow and Business Cycle
Transcript
  Oracle eAM Process Flow and Business Cycle Oracle eAM Process Flow and Business Cycle This document covers the entire business cycle of Enterprise Asset Management with sufficient details to the Business processes and the Sub processes. General Overview of eAM Business Cycle for any Maintenance Organization Creation Of Work Requests Creation Of Work Orders From Work Requests And Safety Procedures Process For Releasing Of The Work Orders Material Issue From The Shop Floor Against Work Orders Work Order Resource Transactions Completion And Closing of Work Orders Failure Analysis Of Assets Maintenance Cost Analysis Preventive Maintenance Schedule Creation Preventive Maintenance Work Order Generation    General Overview of eAM Business Cycle For any Maintenance Organization Description  Whenever equipment breaks down, generally the Equipment operator is the first one to know about it. The Operator will then report about the breakdown to his supervisor. The supervisor, upon taking a note of the problem, will raise a Work request. In the Work request, the supervisor will report the asset number and will also give a brief description of what the problem is. Based on the nature of the problem, he can also assign the work request to a particular maintenance department (mechanical/electrical/Instrumentation). However if the user is not sure which department this breakdown is attributed to, the user will keep it blank. The maintenance user supervisor, upon receiving the Work Request, will designate a person to go to the shop floor and investigate the problem. Sometimes the problem could be a minor one (like a loose connection) and could be rectified in minutes. In that case the maintenance user will rectify the problem and close the work request giving appropriate reasons. If however, the breakdown takes more time to repair, the maintenance user will use the Create WO functionality to directly create a Work Order (henceforth referred to as WO) from the work request.     Against the work order, the user will add all the sequence of operations and against each operation, the user will need to provide whatever resources (internal or OSPs) and materials/spares that are required. In case of OSP items, the user will create a PR and forward it to the purchasing department for raising the PO The maintenance user will then release the WO. Once the WO is released, transactions against that particular WO will be allowed by the system. The maintenance user will now start receiving the PO items (in case of OSPs), charge time (in case of internal resources) and charge material issued from the stores against the WO number and the operation code.  As and when each operation is finished, the user will complete the particular operation. Once the equipment is operational, the user will change the status of the WO to complete stage. The equipment is then under the Trial Run  phase. If the trial run is successfully completed, the user will close the WO order. However, if the trial run fails, then the user will have to un-complete the WO and again add the necessary operations and repeat the cycle against the same WO. Creation Of Work Requests    There are 2 sources of information which can lead to a Work request creation: 1- From the Engineer or technician who is on Site 2- Any Operator, or inspector, any user can report or request (by telephone verbally or through a written form) any problem or service to be done on any asset, this request is to be addressed to the Help Desk Help Desk (who is receiving the call or the request) after his double check on the problem reported will raise a Work Request on the same asset, describing the problem in detail. The Help Desk will receive a notification on this Work Request The Help Desk will also define the Request Type, which can be any of the ones described in the above flowchart The Requestor will (optionally) classify the Request by their priority with the following LOV: Urgent, Normal and Emergency based on the business requirements. The Maintenance Planner will do an investigation, enabling him to approve or to reject the work request. If approved The Maintenance Planner will place the work request on a work order. Creation Of Work Orders From Work Requests And Safety Procedures
Search
Tags
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks