Products
Every product here solves a problem we met on an estate we run.
15 products across four families, additive to IBM Maximo and MAS. Start from the problem that is live rather than the catalogue.
Five routes in
Start from the problem that is costing you money this quarter
Each route names the signal that you are on it, and the move that looks right from there.
A new estate is being stood up
Foundations →You are on it if
A fresh Maximo or MAS instance is waiting on hierarchies, work types, statuses, failure codes and security groups, and data is arriving from spreadsheets nobody owns.
The wrong move here
Letting those decisions land with whoever is free that week. The estate carries them for a decade.
Users find out before monitoring does
Operations →You are on it if
The first report of a failure is a supervisor on the phone, and the same incident has come back three times this year.
The wrong move here
Adding an eighth infrastructure dashboard. Host uptime is true about servers and quiet about whether work completes.
An auditor asks how a change reached production
Operations →You are on it if
The evidence for the last production change is approval email and one engineer's recollection of a Saturday night.
The wrong move here
Writing a heavier change procedure. What is missing is the record, not the intent.
Delivery is sequenced by environment availability
Engineering →You are on it if
A two day change waits three weeks for the only test environment, and releases go in by hand out of hours.
The wrong move here
Buying one more permanent environment. It will be contested within a quarter.
An AI pilot has no write boundary
Intelligence →You are on it if
Readings are transcribed twice, asset data is too inconsistent for a model, and nobody has said who confirms what a model proposes.
The wrong move here
Granting an agent write access to the system of record to prove the concept faster.
Foundations
Day one that already looks like year three.
A new instance arrives waiting for hierarchies, work types, statuses, failure codes, security groups and data. Foundations supplies a considered baseline and a controlled path for the data that follows it.
MaxIron Blueprint
A curated configuration baseline: hierarchies, work types, statuses, failure codes and security groups already set the way your sector runs.
See product →
MaxIron Data Loader
A controlled workspace for bulk Maximo data, with templates for common objects, validation before load and a record of every row rejected.
See product →
Operations
Somebody has to know whether Maximo is working right now.
Operations confirms the journeys a shift depends on, states the cause when one fails, handles the repeats nobody should be woken for, and records every change that reaches production.
MaxIron Cloud Manager
One control plane for every Maximo and MAS environment you run, across whichever clouds they sit on.
See product →
MaxIron Sentinel
Synthetic checks that complete sign-in, work order creation, integrations, scheduling and handheld sync, and name the failing step when one stops.
See product →
MaxIron Diagnose
Turns an alert into a stated cause, the evidence behind it and the alternatives eliminated, with the matching runbook attached.
See product →
MaxIron Autoheal
Runs an agreed playbook against a recurring condition, up to a ceiling you set, and wakes a person outside it.
See product →
MaxIron Change Control
Holds the production gate: who approved which change, what they were shown, and when it was applied.
See product →
Engineering
Ship changes to Maximo the way you ship anything else that matters.
A repeatable path to production, environments created when the work needs them and destroyed when it ends, and upgrades run as a known sequence across a fleet of estates.
MaxIron Pipelines
Collects configuration, scripts, integrations and reports as one versioned release, tests it, and applies it to production with nobody signed in.
See product →
MaxIron DevForge
Creates a clean Maximo environment for one named change in minutes, and destroys it when that change merges.
See product →
MaxIron Upgrade Factory
Runs MAS upgrades across a fleet of estates to a calendar, with the same rehearsal and cutover sequence on each.
See product →
Intelligence
The system proposes, a person confirms, then Maximo is written.
Applied to asset work, AI removes transcription, searching and guessing. Every product here holds the same write boundary, whatever else it does.
MaxIron Nova
Display-first, hands-free inspection and calibration for Maximo. Work on the lens, control via smart ring or smart band, confirmed values into Maximo.
See product →
MaxIron AI Engine
Customer-trained role agents across delivery, support, operations and reporting, each with a review gate and an evidence trail.
See product →
MaxIron AI Smart Data
Classifies, deduplicates and enriches Maximo records in bulk, labelling every inference and who accepted it.
See product →
MaxIron Assist
Answers a user's question on the record already open, from your written procedures, within that user's own permissions.
See product →
MaxIron AI Crew
Executes multi-role work in IBM MAS Manage under scoped permissions, with an approval gate on the write path.
See product →
Enterprise AI is the operating model around these five
The products above work at procedure level. The Enterprise AI pages cover accountability, condition insight, data readiness and where autonomy is withheld.
Explore Enterprise AI →The shape of the catalogue
Sixteen products, and the two or three that matter to you
- 16
- Products across four families
- 4
- Families, in estate lifecycle order
- 2 to 3
- Products a customer typically starts with
Each one built for a problem MaxIron met on an estate it operates.
Stand it up, run it, change it, decide with it.
Chosen against a live problem rather than bought as a set.
Scope of the product family
Additive to IBM Maximo and MAS
Three edges worth knowing before a demo.
Maximo and MAS remain the system of record
Every product here adds operational control, engineering discipline or capture at the asset alongside that platform.
They do not remove the need for decisions
A baseline still needs your process choices. A pipeline still runs your tests. An AI proposal still waits for a person to confirm it.
Most estates need two or three
We would rather scope one product against something costing you money this quarter than sell a set that sits unused.
See any of these in your own environment.
Tell us which problem is live and we demo against your scenario rather than a sandbox. If none of the sixteen fits, we say so.
Bring to that conversation
- Your Maximo or MAS version, and how many environments you run
- The last incident users noticed before monitoring did
- How a change gets from a developer to production, and who signs it off
- Whether an upgrade or a new environment is on the calendar this year