MXH · For Maximo Business Partners

Turn Maximo upgrade discovery into an evidence-backed delivery plan.

Evidence-driven Maximo upgrade intelligence across versions — connecting IBM product changes to what they mean for your Maximo. MXH preserves the technical evidence, groups it into owned readiness work, and supports closure verification after remediation. Your consulting methodology and judgement remain on top.

Run it yourself, step by step

1. Step 1: Get MXH. Request the package and first-run instructions by email at /mxh/start. The core tool is free; metadata packs have separate evaluation and subscription terms.
2. Step 2: Export your Maximo. Your data dictionary, customisation code and screens, plus a manifest. Structure only, no business records.
3. Step 3: Run it. One command over one folder. MXH compares your export with IBM's own release for your target.
4. Step 4: Read the findings. Every difference has a severity, an evidence class, an owner and the test that closes it.
5. Step 5: Use the 13 files. assessment.md, assessment.json, brief.html, report.html, evidence.html, findings.xlsx, mxh.lock.json, architecture.html, assurance.html, engineering.html, explorer.html, preflight-db2.sql, programme.html
6. Step 6: Rerun after fixes. Compare the new run with the original. Closure follows the evidence checked; omitted inputs are never counted as fixes.

Core tool: free. Versioned metadata packs have separate evaluation and subscription terms.

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.
• Readiness work, not a wall of findings. Related observations are grouped into the piece of work that closes them: found, why it matters, do this, done when, owner / when.
• Remediation you can verify. Every finding preserves its closure test. 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: 3 published 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.