Assetize

Work a real Maximo problem on your version, start to finish.

Pick a version and a scenario, work it on Maximo-like screens, break it on purpose, then compare with another version.

Your first run

Click Start here on the lab home. A guide names each step, opens the right screen and highlights the button to click.

  1. Open the script regression on 7.6.1.3.
  2. Inspect the errors, tie them to revision 13, examine the launch point.
  3. Open Test Runs, the Test Bench, and run the tests: input, expected and actual output, and the line that caused each failure.
  4. Apply the right correction for your version.
  5. Run again, compare before and after, open the report.

Scenarios

  • Emergency work order on a failed critical asset (Maintenance Supervisor). Raise the work, meet a stock shortage, reserve an approved alternate, assign qualified labour, issue material and close, on any of the ten industry templates.
  • Inbound integration fails after a mapping change (Integration Engineer). Compare the last good message with the failing one, check the MXAPIWODETAIL contract, correct the mapping and replay the queue.
  • Automation script regression after a deployment (Maximo Developer). Tie failing saves to a script revision and run the test cases in the Test Bench on your version: input, expected and actual output, and the line that caused each failure.

Versions

  • Maximo 7.6.1.3: IBM image demo schema (7.6.1.1) with the 7.6.1.2 and 7.6.1.3 DBC deltas in the lineage index.
  • MAS 8.11 (Manage 8.7): Derived from the 7.6.1.1 schema plus the 8.5 to 8.7 DBC scripts. No capture, no WORKORDER dictionary.
  • MAS Manage 9.0: IBM image demo schema (manageadmin 9.0.378).
  • MAS Manage 9.1: Read-only capture from a running 9.1 lab instance on 2026-09-12.
  • MAS Manage 9.2: IBM image demo schema (manageadmin 9.3.31, Manage 9.2 level) and the 9.2 lab captures.

The Test Bench

Every test case in three parts: the input record, the expected and actual output with a plain verdict, and the script with the culprit line marked. Run the same revision on every version side by side.

Open the lab