Assetize

MXH · Run it yourself

Get MXH. Run it on your own export.

Request the MXH package and first-run instructions by email. Tell us your current and target releases so we can confirm the relevant metadata packs and their terms. Then run MXH on your own export; nothing is installed in your Maximo.

What it costs

Core tool: free. Versioned metadata packs have separate evaluation and subscription terms. This form records a request. Package access and first-run instructions are handled by email.

How you run it

  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.

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

13 sample deliverables: 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. 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.

How to get it

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 the request. How we handle what you send. Once it's stored you'll see: "Request recorded. We'll follow up by email about the MXH package and first-run instructions." The form needs JavaScript. Without it, email aniruddh@assetize.com.au with the same details.