One starts with an implementation project of a maintenance management system. You have chosen a system with care or you have selected an upgrade. With an equal amount of consideration you have approached market players and have selected the best provider. The project plan has been prepared and the project is going to start.
Immediately you will be flooded with questions from the implementation partner and you will be confronted with various decisions that you need to take after the first start up.
Do you recognize this scenario? It does not matter if it is a new implementation or an upgrade. Basically you will be questioned about items you thought the implementation partner had been contracted to answer.
It is a fact that the implementation partner cannot continue its work without these decisions and data. But you are still in the project stage and you do not already have a detailed picture of the possible solution.
At such times it is useful for you to have independent knowledge at your disposal, both in terms of implementation and methodology, as well as a knowledge of the system itself. You can use this knowledge in many different ways
♦ Support your project leader
♦ Re-examining an issue and proposed solution
♦ Judging a design
The possibilities are endless. And with the applied body of knowledge you have control over the project and its desired results.