Tools to understand, modify and enhance Maximo.
Step 1 of 5: Ask. A real answer from our lab.
You: Where is the permit type field on the work order used?
▸ Read the configuration. Nothing changed
WORKORDER.AJSPERMITTYPE is used in 10 places. All 10 are certain.
- Automation scriptAJS_WOVALIDATE raises an error when a permit is needed and the type is empty.
- Communication templateAJSPERMITREQ puts the permit type in the email text.
- ScreenWork Order Tracking shows the field.
- Security restrictionGroup AJSPLANNER: the field is required under one condition.
- Related objectsWOACTIVITY, WOCHANGE and WORELEASE each carry the same field.
An illustration of the workspace. Steps 1 to 3 show real answers from our lab systems, which hold made-up customisations. Steps 4 and 5 are in development and show how a change will work.
From the makers of AJAEX Tools for TRIRIGA and MREF

Understand
The questions that usually wait for whoever remembers the history.
The tools read Maximo's own configuration and change nothing. You ask through an AI assistant, and each answer names the rows it came from.
- 162
- configuration tables read, across 15 areas of Maximo
- 26
- read-only tools an AI assistant can call
- Every row
- and every column checked against the database
Where is this field used?
Every script, screen, workflow, template and security rule that names an attribute or object, each marked certain or possible.
What does this workflow do?
The steps, conditions, actions and roles of a workflow, and the escalations and cron tasks that run beside it.
Who can do what?
Which security groups can open an application or use an option, and which restrictions apply.
What is on this screen?
Each control on a Maximo screen and the field it is bound to, and how a screen differs from the one IBM ships.
What have we customised?
Objects, attributes, domains, scripts, screens and custom Java that are not in a clean install of your version.
What talks to what?
Object structures, publish channels, enterprise services and end points, and the scripts and classes that sit on them.
In early access. Proven on Maximo Manage 9.1 in our lab, on a system seeded with known customisations of every kind: each tool finds exactly what was planted. We test it with 42 questions a Maximo contractor would ask.
Upgrade
Know what the move to Manage 9 will touch.
We compare three things: a clean install of your version, a clean install of the version you are moving to, and your system. What is left is what you changed, and where it meets what IBM changed.
Your database administrator runs one read-only export of the configuration tables. No business data leaves, and passwords and keys are left out.
| Between 7.6.1.0 and Manage 9.1.408 | IBM added | IBM removed |
|---|---|---|
| Objects | 183 | 11 |
| Applications | 224 | 17 |
| Attributes | 2,346 | 115 |
Counted by our comparison of clean installs of both versions.
What the assessment tells you
- What you have customised, area by area
- Where your changes collide with IBM's, by object, domain and application
- Custom Java, and shipped classes you have extended
- Automation scripts at risk
- What IBM removed that you still use
- What a snapshot cannot show, stated plainly
The export runs on Db2 today. Oracle and SQL Server follow.
Modify and enhance
Then change it: plan, approve, apply, verify.
Describe the change you want. The tools plan it against your configuration and name every object it touches. A person approves it, the tools apply it, and they read it back to prove it.
It is the pattern we built for AJAEX Tools for TRIRIGA and MREF: read first, and change only once the reading can be trusted. Adding an attribute already works in our lab.
Early access
Be one of the first systems we assess.
Tell us which version you are on and where you want to get to. We'll show you the tools on our lab system and agree how to run them on yours.