CMMS Software Upgrades - Know your requirements before....

This post builds on the previous post "CMMS Upgrade - Lessons Learned"  that highlights some of my experience with upgrading CMMS system versions. Software implementation and/or updates should be treated like a hard asset project. Exercising the same framework and best practices utilized in past projects will provide the project team with familiar communication processes and methodologies to enable success. Typically software system updates are CAPEX funded so....you have a defined scope, a list of deliverables and desired output of the product service and result. Often the project team will consist of, and will be relying on, consultants acting as subject matter experts. There often are certain expectations when working with third party groups. Acknowledging this, documentation of deliverables, associated risks and assumptions is key to managing the project. This may be an iterative process which most likely will adopt a rolling wave planning methodology. The benefits of this type of plan will enable the Project Manager to identify and remove, or at least manage risks that could impact future events. If one deliverable is not achieved, the project could be seen as a failure, which could impact confidence and the ability to have future projects approved. Although the thought of losing short term confidence is a major influence in managing a project, the ultimate impact is realized for an extended term as the effects of the missed deliverable(s) are realized. Understanding and documenting the potential impacts of deficiencies within the defined deliverables will empower the steering committee to make satisfactory decisions.
In closing...define the desired outputs and input the hold points necessary to meet all deliverables.