Hi,
The following summarizes the contents of a typical post-implementation review report, the approach proposed here is applicable to any maintenance improvement project under review.
The review document
The report's first section describes the methodology used for gathering information. Most reviews have two parts: extensive interviews and perusal of documentation. The people interviewed should represent each stakeholder group involved in the project, including maintenance management, maintenance technicians, operations management and workers, senior management, accounting, information technology, engineering, purchasing and the CMMS vendor. The report should list the people interviewed.
It's useful to have a list of standard questions to guide each interview. Some sample questions include:
What was the purpose of the project?
What did you like about the implementation process?
What things would you change if you had to do it again tomorrow?
Were your expectations met? Why or why not?
Was communication effective throughout the process?
Project objectives
It's important to reiterate the original purpose behind implementing to ensure the original objectives were met. If the objectives were clearly stated at the project start, then that material copied from a previous document is sufficient. It's surprising how often objectives weren't clear, as evidenced by the range of responses to the first question above. Focusing on a few well-communicated objectives is key to ensuring a successful project.
Issues and recommendations
The bulk of the review should identify issues from each stage in the project, recommendations for eliminating outstanding issues and suggestions for preventing a recurrence. Consider some of the more common issues below.
The definition of requirements is the first potential trouble spot. Common complaints regarding development of the specifications include failure to:
Involve every key stakeholder.
Develop specific requirements that can differentiate among vendor offerings.
Prioritize the requirements.
Establish requirements for the next three to five years, rather than focusing on replacing the current system.
Determine the process changes required to enable the CMMS.
Vendor selection also has common issues, including:
Lack of a formal vendor selection committee.
Failure to follow a methodology mutually agreed to by all stakeholders.
Omission of critical steps in evaluating vendors, such as site visits and reference checks.
Failure to speak to someone other than the project champion during site visits and reference checks.
Improper or inconsistent documentation of vendor ratings, which makes vendors feel that they were treated unfairly.
Testing of candidate packages, too often, is merely a vendor's demonstration. Effective reviews, on the other hand, require you to provide the vendor with test scripts to demonstrate that the CMMS can manipulate your own real data and produce reports in accordance with your specifications. The vendor should test customized software or configuration changes fully before delivery. Other forms of testing include hardware testing, stress testing (ensuring the system can handle peak volumes), integration testing (passing data to and from accounting, shop-floor data collection and ERP systems) and conducting a pilot.
Installation of software and hardware is almost always fraught with problems. The key to avoiding such struggles is to anticipate potential problems, have resources and a methodology for dealing with them, and establish a viable escalation procedure, if required. Some common issues include:
Stakeholders' acceptance of new systems and procedures.
Project timing.
Integrating multiple vendors.
Training can be a problem. The more usable the software, the less training is required. However, many companies underestimate the importance of training sessions. It's important to motivate users to adopt the new procedures to realize the benefits of implementing the software.
Vendor support plays a key role throughout and long after the CMMS implementation. The review should identify ways to improve vendor relations, including:
Clearly articulated service-level agreements for response time.
Performance incentives and penalties.
Effective train-the-trainer programs for an in-house help desk, ongoing training and using advanced features.
Cost analysis often reveals unanticipated cost overruns. The review should examine the implications of cost variances and suggest ways to improve future cost estimating.
Business impact is another point. The most difficult task for a project manager is to harvest the benefits that the original business case promised. The review should revisit the business case to determine its completeness, relevance and degree of success in achieving benefits.
Although headcount reduction is a fundamental consideration in any business case, it's rarely a direct result of installing a CMMS. The review should examine other benefits.
Customer satisfaction must support the promises of more satisfied external and internal customers (operations), which were almost certainly made to justify purchasing the CMMS in the first place. The review must identify whether benefits, have accrued as projected.
Employee satisfaction can be the result of a successfully implemented CMMS package because the CMMS, coupled with proper procedures, ensures the following:
The right parts are kitted ahead of time.
The operations department schedules equipment downtime before the maintenance technician arrives.
A history of work done on the equipment and its components is attached to the work order.
The review also should explain any variances between the predicted and actual level of employee satisfaction.
Productivity improvement is the most common rationale to cost-justify CMMS packages. The review should examine any such claims and recommend ways to mitigate unfavorable variances.
Appendices
The final report section provides detailed documentation of related material, such as the list of people interviewed, a summary of interview questions, a log of detailed issues that arose during the project, and other relevant documents.
regards
vivek
Edited by: Vievk Vardhan on Nov 19, 2009 2:34 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.