When a "Solution" is not a Solution

Most asset owning and operating organizations managing maintenance activities use a computer system – either a CMMS, or an EAM, or possibly a module in their ERP. Usually they want to sustain reliable performance of their assets to deliver high availability to their operations or production groups. These systems are often sold under the moniker, “solution”. Implied in that is the solution to some sort of a problem, one might imagine that it will deliver high reliability, or better maintenance practices, yet they don’t and can’t. Many have fallen victim to slick marketing, buzz words, and promises of functionality that are little more than dreams – vapourware. To get those practical business results you need to change what you are doing and how you are doing it, not how you are tracking it and managing the activities. Those systems do provide some help with data storage, reports, keeping organized and work flows, but they don’t help you define what work to do, nor how often, nor who should do it, they don’t do anything to ensure you actually do the work, and then record what you did with any accuracy. The result is often a system that is riddled with inaccurate, incomplete, or otherwise unfit data that can actually make work for, and be misleading to the system’s users. Interestingly, after seeing hundreds of different instances of different systems in a large variety of organizations, there are some common problems. If you are a supplier of these systems, you can probably relax now. Very few of the problems m have anything at all to do with the software itself. This presentation will explore the reasons for those disappointments and some of the possible solutions.