MXH · For Maximo Business Partners

Scope a Maximo upgrade from evidence, and hand the client a document that survives being checked.

Evidence-driven Maximo upgrade intelligence across versions — connecting IBM product changes to what they mean for your Maximo. MXH produces the assessment; your name goes on the cover.

Five business days, from export to files

1. Day 0: Export received. Your dictionary, code and screens arrive. The clock starts here.
2. Day 1: Run against target release. Your export is compared with IBM's own release: upgrade scripts, compiled API, screens and dictionary.
3. Day 2: Graded findings. Every difference gets a severity and an evidence class.
4. Day 3: Owner review. Each finding gets its owner, its action and the test that closes it.
5. Day 4: Seven files delivered. assessment.md, assessment.json, brief.html, report.html, evidence.html, findings.xlsx, mxh.lock.json
6. Day 5: Rerun after fixes. Same inputs, same report. Your fixes show up as closed.

Founding Partner Pilot A$4,950 ex GST · Standard A$9,900 ex GST · Additional environment from A$3,500 ex GST.

What it changes about a scoping engagement

• Scope from the system, not from an interview. Every finding cites the object, attribute, class or control it came from, and the file and line in the client's own code that touches it.
• Defensible under challenge. Each finding carries how strongly it is evidenced and what that evidence does not support, so a client's own architect can check it and find it holds.
• Remediation you can track. Every finding names an owner and the test that closes it. Rerun against the fixed system and every finding lands in one of 7 named outcomes, with the original record preserved.
• Reproducible. Same inputs, same rerun id, byte-identical reports — so two people running it get the same answer, and so can the client.

On the cover

Your name and contact block go on the partner documents. That is presentation, not an authorship claim over the findings, and it is stated as such. No report carries any implication of IBM endorsement, and none carries an effort or cost figure — MXH counts sites; converting sites to days is your judgement about your team, and it is not ours to fake.

What the client has to send

A data dictionary export, their customisation source, their screen exports, and a manifest declaring the release, the industry solutions and anything they are not sending. A REST fetcher ships with the product, so a site can pull it over the API instead of running a database export. Nothing needs to be installed on their Maximo.

Before you send anything

The base-release numbers are already published: 10 release-to-release moves and 12 staged-versus-direct comparisons, computed with no customer data at all. Read them here — they are the floor. A client's own system only ever adds to them.