Assetize Lens · Scoped pilot · Product intelligence for IBM Maximo
Every click in your Maximo, in plain English.
Maximo's screens send each click to the server as an event, and nobody can read those events. Assetize Lens can. It shows which screens your people use, where the minutes go, which licences you don't need, and how each workflow really runs. Then it helps you fix them.
533 apps mapped, 7,482 menu options traced, 26,608 screen controls decoded, across four releases from 7.6.1 to 9.2.
Everything product teams get from analytics, built for the way Maximo works.
- AppPoints right-sizing: who needs Premium, who needs Base, and who only ever reads.
- Real usage: which apps, tabs, actions and fields each group uses, by site and role.
- Where the time goes: request to work order to approval to done, with the minutes lost at each step.
- Heatmaps that become fixes: fields nobody fills and tabs nobody opens, turned into a simpler screen.
- Session replay, errors with their story, slow screens named, safe rollouts and an upgrade lens.
Draw your workflow. Export a migration package.
A drag-and-drop workflow designer covering every node type, checked as you draw, that exports a Migration Manager package with the roles, actions and communication templates the process needs.
Your customizations and IBM's updates, kept in sync.
Lens reads your apps and screens from your own Maximo, and every IBM release is re-mapped and compared with the one before. The comparison feeds the Change Watch.
The decoding layer is ours, and it grows with every release.
Built on the same evidence as MXH, the UI playground and the knowledge base.
First proof: a live Maximo 9.2, decoded end to end.
The Usage X-Ray is a scoped pilot, not general availability. Its proposed output is usage by app and role, slow or repeated steps and prioritised improvements, with the observed period and coverage stated.
We need an agreed capture of representative interactions or compatible event logs, plus app and role context. Custom-screen decoding also needs presentation metadata. Read-only access alone does not provide historical usage. We agree the capture setup, observation period, access and data handling before the pilot; the lab currently uses a capture pod.