Guideline for Selecting CMMS Software

While selecting a CMMS (Computerized Maintenance Management System) we must see that it is able to do the following takes. The list is only indicative and may vary from client to client.

Guideline for Selecting CMMS Software


Work Order:

1. Produce an easy-to-use work order that allows future conversion to a more sophisticated system.
2. Classify all work by some kind of repair reason code: PM, corrective, breakdown, management decision, etc.
3. Automatically coat work orders. Loos up the value of a part in the inventory and bring the cost across to the maintenance work order. Also, look up the chafe rate for the individual mechanic.
4. Provide the status of all outstanding work order Allow sorts on different status codes. An example would be to print or display all work orders waiting for engineering.
5. Record maintenance request calls (who, what, timestamp, where, how), which can be printed in al long format.
6. Allow production to find out what happened (what status) to their work request without being able to make changes.
7. Calculating backlog of work and display it by craft.
8. Both open and closed work orders can be displayed or printed very easily. Keep work order available for the five years, and preferably from birth to retirement of the equipment.
9. Facilitate labor scheduling with labor standards by task, ability to sort and restore the open work order by location of work, craft, and other ways.

Spares Parts Control:

10. Produce lists of spares as per various analyses such as XYZ, ABC, FSN, and VFD.
11. Help the mechanic or storekeeper to find infrequently used spare parts.
12. Generate a part catalog by type of part or by the current vendor, with yearly usage to facilitate blanket contract negotiation
13. Automatic linking of equipment data with spare part data.
14. Recommends stock levels, order points, order quantities and automatic reordering of spares based on the inventory control logic.
15. Generate he reported on consumption, inventory levels, out of stock material, material receivables, etc.

Maintenance History and Reporting:

16. Maintain maintenance history for each asset that is detailed enough to tell later what happened years.
17. Provide information to tack the service request- maintenance- order issues- work order complete- customer satisfying cycle. Include elapses time and other analysis factors.
18. Provide the report for budget, staffing analysis, program evaluation, and performance.
19. Provide information for work planning, scheduling, and job assignment. Has the capability to store and retrieve work plans, copy old work plans and modify existing plans when new information comes in.
20. Be able to isolate all work done (sort, arrange, analyze, select, or list) by work order, mechanic, assets, building, process, product, division, floors, room, type of equipment or asset (This is most important as we can generate reports according to various categories)
21. Provide the ability to easily structure as hoc (on the spur of the movement) reports answering the question that comes up. This skill is called to report writer.
22. Has the ability to generate equipment /assets history from birth (installation, construction, or connection) to present with all major repairs and summaries of smaller repairs.
23. System reports are designed around the Pareto principle where the system helps identify the few important factors and helps you manage the important few versus the trivial many.
24. System reports on contractor versus in housework. A system can track contractor work in as many details as in housework.
25. Provide reports charging back maintenance costs to the department or cost center.
26. Provide downtime reports, active and pending work order reports.
27. Have reports with a mean time between failure (MTBF) that shows how often the unit has failed, how many days (or machine report) lapsed between failure and the duration of each repair (MTTR).
28. Highlight repeat repairs when a technician needs some help.

PM System:

29. Allow mechanism to easily write up deficiencies found on the PM inspection tours system then automatically generates and tracks a planned maintenance work order.
30. Automatically produce PM work orders on the right day. PM system can sort work orders by location to minimize travel time.
31. Be able to display PM workload for a future period such as a year by week or month by trade.
32. Be able to record short repairs done by a PM mechanic in addition to the PM and actual time spent.
33. Support multiple levels of PM on the same asset(such as a 30-days A-level and a 180 day-B- level on the same asset) re-set the clock if the high level is done. (If you do a yearly rebuild, the monthly PM clock gets reset). A resetting feature prevents a 30-day PM coming up a week after a rebuild.
34. PMs are generated by location bt trade to facilitate efficient use of people and minimize travel.

General:

35. The system should be able to handle 3-4 times more assets than you imagine ever having. Even medium-sized and smaller companies go on acquisition hunts. A small successful manufacturer might find themselves tripling (or more) in size overnight.
36. The system should be user-friendly and should incorporate help feature and too tip features so that the user is comfortable in using the system. It should be easy to use and learn for beginners and quick to use for experienced users.
37. The system should be appropriately supported by the vendor with technical help such is up-gradation, error fixing, integration with other networks, Internet intranet, etc.
38. The system tracks the warranty for components and flags warranty work to recover funds.
39. The system is integrated or can be integrated into purchasing, engineering, payroll/accounting.
40. The system enables reports reporting of emergency maintenance, which are not scheduled after they are completed.
41. The system easily handles a string PM such as lubrication rout, filter change route.
42. The System runs on standard computer hardware (not special hardware incompatible with everything else). The system is compatible with existing Local Area Network (if it is a PC product).
43. The system vendor has the financial strength to complete the contract (and stay in business for several years after installation)
44. The vendor has software support people whom you can easily reach.
45. The vendor provides economical customization. They have ongoing enhancement. The Programmer is the employees of the vendor or contract workers.
46. The vendor has a local installation organization.
47.  The vendor is experienced in the management of installation projects of the size of your facility; they have start-up experience with projects this size.