0% found this document useful (0 votes)
84 views

EAM Process Flowchart

When equipment breaks down, the operator reports it to their supervisor who creates a work request describing the problem and assigns a maintenance department. A maintenance user investigates, and either fixes minor issues immediately by closing the request, or creates a work order to track a longer repair process. The work order outlines operations, resources, and materials needed. Purchase requests are made for outside services and a work order is released once items are received. Operations are completed and the equipment put through a trial run, closing the work order if successful.

Uploaded by

wasif_ahmed_4
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
84 views

EAM Process Flowchart

When equipment breaks down, the operator reports it to their supervisor who creates a work request describing the problem and assigns a maintenance department. A maintenance user investigates, and either fixes minor issues immediately by closing the request, or creates a work order to track a longer repair process. The work order outlines operations, resources, and materials needed. Purchase requests are made for outside services and a work order is released once items are received. Operations are completed and the equipment put through a trial run, closing the work order if successful.

Uploaded by

wasif_ahmed_4
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Process Flow Description Whenever equipment breaks down, generally the Equipment operator is the first one to know

ow 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.

You might also like