Assetize

MXH · Free download

Get MXH. Download it free and run it on your own export.

One command installs MXH with every metadata pack. Then mxh ui opens it in your browser, or run the same commands in a terminal. No key and no sign-up. Nothing is installed in your Maximo.

Install it

Windows, in PowerShell (no admin rights needed):

irm https://assetize.com.au/mxh/install.ps1 | iex
mxh ui

macOS and Linux:

curl -fsSL https://assetize.com.au/mxh/install.sh | sh
mxh ui

Prefer a file? Download mxh.jar (MXH 0.13.0) and its SHA-256, then run java -jar mxh.jar ui. Step-by-step install.

MXH needs Java 17 or newer. mxh doctor checks your machine and names the next command.

What it costs

Free: the tool and the metadata packs. The code is Apache-2.0, and the metadata packs are free to use for any purpose, on any number of machines. Passing on an unmodified MXH release is fine; the one ask is not to republish the packs as a dataset. Read the licence.

How you run it

  1. Step 1: Get MXH. One command installs it, free, with every metadata pack. mxh ui opens it in your browser.
  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: Open the reports. Start with readiness.html, then the brief, the full report and the explorer. findings.xlsx and assessment.json feed your own tracking.
  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.

Free: the tool and the metadata packs.

The step-by-step guide covers what to export and the three ways to run it.

What goes in

One folder: your data dictionary export (objects, attributes, relationships and domains, as CSV or JSON), your customisation source (Java, automation scripts or both), your Application Designer screen exports, and a manifest that says which release you run, which industry solutions are installed and anything you're holding back. A REST fetcher ships with the product if a database export is hard to get.

What comes out

16 sample deliverables: readiness.html, brief.html, explorer.html, report.html, programme.html, architecture.html, engineering.html, assurance.html, evidence.html, findings.xlsx, assessment.json, assessment.md, readiness.json, readiness.md, mxh.lock.json, preflight-db2.sql. Every finding is graded, carries its evidence class, names an owner, states the action and states the test that closes it. The report also says what it didn't assess.

See what a run produces: 22 findings, 7.6.1.3 → 9.2. How an assessment runs.

Want a hand with your move?

Tell us your releases and we'll reply by email. The form on this page asks for:

  • Your name, work email and company.
  • Whether you're a Business Partner or an End client.
  • The release you run today: 7.6.1.3, 9.0, 9.1, or other / unsure.
  • The release you're moving to: 9.0, 9.1, 9.2, or other / unsure.
  • The industry solutions you run, from the 18 MXH knows.

Don't send an export, credentials or a system URL with it. How we handle what you send. Once it's stored you'll see: "Thanks. Your message is saved, and we'll reply by email." The form needs JavaScript. Without it, email aniruddh@assetize.com.au with the same details.