IBM Maximo is not an out-of-the-box solution, but a versatile toolkit. With it, we set up an asset management solution that optimally supports your work processes. Every change to your IBM Maximo environment must happen in a validated, controlled manner. Because what you absolutely do not want is for important work processes in your organization to be disrupted. How do you prevent new functionality from not working properly, being incomplete, or going live too early?

Inventory desired changes

From developing, testing, and validating to acceptance

Once a month, we release a new version of IBM Maximo for the client. All agreed changes are implemented in that release. Several steps precede the go-live, in which we work in various IBM Maximo environments. We start with building in the development environment and then move to the test environment. There, we test the release and validate whether all intended changes are included. The next step is to bring the release to the acceptance environment. In that environment, the client tests for themselves whether everything works as intended. In this case, they do that at their own discretion, but we can also play an advisory role in this.

Securing release process

During the building of a change, we record all the details. We do this in an ‘as built’ document developed by Gemba. Such an as built document is linked to the corresponding service request in IBM Maximo and is therefore always easy to find. Prior to the monthly release, we combine all as built documents into one overall summary. This also states, for example, how much downtime is involved with the implementation, what the risks are, and what measures have been taken to minimize those risks. This document goes to the client’s change advisory board, which gives it a final approval. This ensures that the entire release process is solid and secured. After the release, we synchronize the development, test, and acceptance environments. Everything must be the same in every environment, because otherwise this may cause problems with subsequent changes.

Continuous improvement