Products
Software for the Maximo work your team needs to improve.
Start with operating the estate, moving data, field work, controlled assistance, or releasing a change. We will show the relevant product and where its responsibility ends.
Choose by need
Choose a product for the work you need to improve
Choose the product for bulk data work, field execution, controlled assistance or software delivery. Each has a defined role alongside IBM Maximo and MAS.
Operate and monitor Maximo
MaxIron PortalOne tenant-scoped workspace for environments, service health, delivery runs, approvals and governed Assist work.
Bulk operational data work
Data LoaderQuery, create, update, sync or delete records in a shared workspace, with a dry run and row-level result.
Formal master-data approval
Data GovernanceFreeze a proposed revision, separate maker from checker and retain the decision.
Technician field execution
MobileComplete assigned Maximo work on a phone, including predictable offline work.
Hands-free inspection capture
NovaPut the reading and confirmation in the technician’s view while their hands remain on the task.
Answers and controlled actions in Maximo
AssistFind live Maximo records, prepare narrow actions and wait for the signed-in person to confirm.
Build and release a change
Portal delivery toolsApprove, test and move Maximo changes through a repeatable release path.
The operating platform
One authorised workspace for the estate
Operators sign in once and see their authorised tenants. Portal brings together environments, service health, alerts, recovery workflows, production approvals, releases, test environments and fleet upgrades.
Portal is delivered on the Maximo and MAS estates MaxIron operates. IBM Maximo remains the system of record for assets, work orders and history.
Explore MaxIron PortalPortal surfaces
Four operating needs
- Know what is running See Maximo environments by tenant, with service state, cloud resources and the costs available to that operator.
- Find and resolve a service problem Check the user journey, bring likely causes together and run an agreed recovery with a retained record.
- Approve and release a change Keep the approval beside the tested change and move it through the same release path each time.
- Deliver across several estates Create short-lived delivery environments and apply a planned upgrade sequence across the fleet.
Move and govern data
Load operational data, control master-data changes, or start from a considered baseline.
A new instance still needs hierarchies, work types, statuses, failure codes, security groups and data. Choose a considered baseline, bulk data work with a dry run, or formal master-data change with approval.
MaxIron Blueprint
A working baseline of statuses, domains and security groups gives process owners a concrete starting point for design.
See product →
Flagship product
MaxIron Data Loader
Bulk query, create, update, sync and delete of IBM Maximo data in a shared browser workspace, with a dry run against Maximo rules, scheduled jobs and a record of each row.
See product →
Flagship product
MaxIron Data Governance
Asset, location and item changes in Maximo Manage go through a request someone owns: frozen revisions, maker-checker, stale-record protection and retained evidence. Each deployment is configured and validated for the customer environment.
See product →
Equip field technicians
Complete Maximo work where the technician is.
Technicians complete assigned IBM Maximo work on a phone. Offline changes stay queued. Calibration uses the Maximo datasheet. Nova can propose a reading the technician still confirms. IBM Maximo remains the record.
MaxIron Mobile
Technician app for assigned IBM Maximo work on iOS and Android, with a visible offline queue, labour timer, calibration datasheets and optional Nova capture.
See product →
Flagship product
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 →
Automate controlled work
Give people faster answers without giving software unchecked authority.
Applied to asset work, Assist answers beside the signed-in Manage user. Writes wait for confirmation. The same product can run longer role work in Portal and propose data changes for a person to accept.
Build and release changes
Move tested Maximo changes through named environments and approval gates.
Change Control records the decision. Pipelines move tested changes. DevForge provides an environment for one piece of work. Upgrade Factory applies a planned sequence across several estates.
MaxIron Change Control
A named approval and retained record before software or configuration moves into production.
See product →
MaxIron Pipelines
Repeatable release paths for tested Maximo configuration and scripts.
See product →
MaxIron DevForge
A short-lived Maximo environment for one change or delivery task.
See product →
MaxIron Upgrade Factory
A common upgrade sequence and calendar across several MAS estates.
See product →
Also from MaxIron
OrqForge for governed AI agent work
OrqForge runs governed AI agent work with review gates and an evidence trail. It is a separate platform from the MaxIron products for IBM Maximo and MAS. Product details, roles and the demo are at orqforge.com.
Scope of the product family
Additive to IBM Maximo and MAS
Agree responsibilities for Maximo records, product access and deployment before a demonstration.
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. We review the relevant product against your scenario rather than a sandbox. The first finding is which product, and which Portal or Assist surface, the work belongs in.
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