MXH · For the person signing

Know the size of your Maximo upgrade before you sign for it.

We read your Maximo, your customisations and your screens, then hand you the full list of what has to change to move to the new version. Every item has a name against it and a test that proves it is done. You get that list before you commit the budget, not halfway through the project.

IBM has already set your deadline

We did not make these dates up. Each one is on an IBM support page you can open yourself.

Watch the 2027 one. If you traded up to a MAS licence and kept classic Maximo running alongside it, that arrangement stops on 30 April 2027. On a Perpetual Trade-Up you are then not just unsupported. You are out of licence.

We find the part nobody has written down

IBM ships the new version and it works. The budget goes on your own stuff: the customisations, the columns someone added in 2014, the interface expecting thirty characters that now gets a hundred, the screen a contractor built and never documented.

We find those, count them, and name an owner for each. You see them now instead of in testing or on go-live weekend.

Something you can hold people to

Each item on the report says who fixes it, what they have to do, and the test that proves it is done. So when someone tells you an item is closed, there is a stated test that says whether it is.

Run it again after the fixes and everything sorts into four piles: fixed, changed, still open, and new problems the fixes caused. The first report is kept, so nothing quietly disappears between one steering meeting and the next.

Same inputs, same answer, every time. Two people running it get the same result. So can your auditor.

You get a count you can trust, and make your own estimate

We count the exact places in your code that have to change, and show you the evidence for each. Your team or your partner turns that into days, using what they know about your people, your test environments and your change windows.

You get the counts: how many sites, graded, owned, each with the test that closes it. Your delivery team puts days and rates against them, because your people and your rates are yours to know.

Three files and we can start

An export of your data dictionary, a copy of your customisation code, and your screen exports. We install nothing on your Maximo and touch nothing in production. Send what you have — the report names exactly what it checked, so you always know what a clean result covers.

One question for your team

Not "can we upgrade". You can. Ask them this: how many places in our own code break on the new version, and who owns each one?

If nobody can give you a number, nobody has looked. Here is what the answer looks like for a real customer.

Send the right person to the right page