Assetize

MXH / Maximo upgrade assessment

Find the work your Maximo upgrade needs.

Compare your Maximo configuration and custom code with your target release. Get a fix list with evidence, owners and a clear check for completion.

Core tool: freeRuns locally on your export
Get MXH See real examples

Versioned metadata packs have separate evaluation and subscription terms. Access details

Request the package and first-run instructions by email. Your exports stay with you.

Real customer assessment · anonymised

Different findings.
Different work to do.

Three examples from a real assessment: a configuration review, a code change and a business decision.

Indicative scope / Easy

Review a user-sync setting

How it was found
The configuration export contained an enabled legacy integration-response setting.
Why it matters
This setting has been associated with MAS user-sync failures.
Next actionReview the target configuration and test a complete user-sync cycle.
Owner and closure check

Owner: Maximo administrator

Close it when: A test user is created or updated in MAS and appears correctly in Manage.

Indicative scope / Medium

Make time conversion explicit

How it was found
A script configured as active used the server’s default time zone to produce a UTC-labelled result.
Why it matters
A different target time-zone configuration could change its output.
Next actionMake the intended conversion explicit. Compare representative dates, including daylight-saving boundaries.
Owner and closure check

Owner: Script developer and platform owner

Close it when: Agreed source and target records produce the intended matching times.

Indicative scope / Hard

Resolve legacy mobile dependencies

How it was found
An administration screen referenced three Anywhere objects removed from the target. The findings remained after assessment refinement.
Why it matters
The team must decide which capability is still needed; a code edit alone cannot settle that.
Next actionRetire unused dependencies and replace retained capability, then test it on the target.
Owner and closure check

Owner: Mobile/business owner and solution architect

Close it when: Retirement or replacement is approved, and retained journeys pass target acceptance.

From a real 7.6.1.3 → 9.2 assessment. Easy, medium and hard describe indicative work scope, not measured effort. These findings were identified and investigated; completed remediation is not claimed.

A report your team can work from

Know the work. Assign it.
See what’s changed.

Scope the upgrade work

See the changes that affect the inputs you supply, with evidence and stated coverage to support your planning.

Give each fix an owner

Findings name the affected item, required action, responsible role and the check that closes it.

Verify progress

Rerun after remediation. Keep resolved, changed, remaining and unassessed work visible against the original run.

Self-service. Run it on your own export.

From your export
to a fix list.

  1. Export

    Gather your dictionary, custom code and screens. Add configuration or security exports where relevant and declare anything omitted.

  2. Compare locally

    Run MXH over that folder with the source and target releases you chose. Nothing is installed in your Maximo.

  3. Act and rerun

    Use the brief, technical findings and workbook to assign work, then compare a new run after fixes.

See the inputs and deliverables

Know the scope

What MXH checks today.

Coverage follows the releases, packs and inputs you choose. Missing inputs stay visible in the report.

Upgrade paths from Maximo 7.6.1.3.
Available targets: 9.0, 9.1, 9.2.

Read the coverage details
Explore a release move

71 script-stated changes. The same list direct, via 9.0 or via 9.1.

7.6.1.3 → 9.2. Distinct changes, combined across each route. Delivery effort, testing, downtime and supported-route prerequisites are assessed separately.

Open the release comparison

For developers: modelled tests

A separate local harness for supported scripts and MBO behaviours, with stated rules and assumptions.

Static checks

Dictionary and custom code

Compare supplied definitions, Java or JAR references and automation scripts with the selected release evidence.

Static checks

Screens, configuration and security

Inspect classic presentation XML, role-based app definitions and supplied configuration or security exports. Missing inputs stay visible.

Modelled locally

Developer behaviour tests

Exercise supported scripts and MBO behaviours in the local harness. The model states its rule coverage and assumptions.

Target evidence

Target-side closure checks

Your team runs checks that require the customer target, such as report rendering and operational behaviour. Use those results as closure evidence.

Start with your own Maximo.

Request the package and first-run instructions by email.

Get MXH