MAS suite
Nine MAS applications, routed by the decision in front of you
Manage carries assets, work and inventory. This page routes to the nine applications on top of it, each with the prerequisite that decides whether it pays back or produces a screen. MaxIron configures, integrates and operates all nine on the same managed cloud as Manage.
Table one
The decision you arrived with, and the application that answers it
Read the third column before the first. The prerequisite decides the outcome, not the licence.
Monitor binds SCADA, historian and edge signal to asset records and opens anomalies against them.
How we deliver Monitor →You are on it if
Operating data sits in the historian and never reaches the planner who could act on it.
The wrong move here
Binding tags at a location covering forty pumps, so the anomaly names a station.
Predict estimates failure probability from coded failure history and condition signal.
How we deliver Predict →You are on it if
The board has asked for failure prediction rather than reaction.
The wrong move here
Starting on the largest bespoke machine on site, where no population exists to generalise from.
Health scores condition, criticality and consequence for every asset on one basis.
How we deliver Health →You are on it if
A capital submission, a maintenance budget or an ISO 55001 audit has to be defended.
The wrong move here
Scoring before consequence is agreed with operations, safety and finance.
Visual Inspection runs image and video models against a written defect dictionary.
How we deliver Visual Inspection →You are on it if
Inspection findings vary between inspectors and the volume keeps rising.
The wrong move here
Training on images nobody tied to an asset record or a named defect class.
The IoT and OT layer moves plant data across the boundary and maps tags to assets.
How we deliver the OT layer →You are on it if
The OT team has refused the last three requests for plant data.
The wrong move here
Asking the control layer for the data, which is the request OT is right to refuse.
Renewables ingests SCADA and OEM portals and raises the work in Manage.
How we deliver Renewables →You are on it if
Wind, solar or storage assets from several manufacturers report in several portals.
The wrong move here
Ingesting portals before one asset structure is agreed across the contract and Manage.
Field Service Management adds Scheduler, Optimizer and Spatial to the Manage work record.
How we deliver FSM →You are on it if
The dispatcher spends the shift moving jobs rather than handling exceptions.
The wrong move here
Optimising against job durations the field does not believe.
Real Estate and Facilities holds leases, space and building services on MAS.
How we deliver IWMS →You are on it if
Lease dates, space data and building requests live in spreadsheets.
The wrong move here
Reusing plant work types for facilities requests, which loses the space hierarchy.
Maximo Mobile gives technicians and inspectors an offline front door to Manage.
How we deliver Mobile →You are on it if
The field still works from paper or from a desktop screen in the mess room.
The wrong move here
Shipping every work type at once instead of the two the trade uses daily.
Table two
Three dependency tiers, which is the classification that changes your plan
Group by what each application depends on. That decides what starts this year and what waits for data work.
| Ref | Applications | What it reads | First scope we take | Skip the foundation and |
|---|---|---|---|---|
| T1 | Monitor, Predict, Health, Visual Inspection | Manage hierarchy, criticality, classification, failure coding, work history and images held against asset records. | Readiness assessment on one asset class, then remediate that class alone. | A confident output describing the wrong estate, and a screen nobody opens after a fortnight. |
| T2 | Real Estate and Facilities, Renewables as a standalone performance tool | Little from the legacy register. Space, lease and generation structures are established during implementation. | One building, or two sites from different manufacturers, with the identifier scheme agreed before ingest. | Less exposure to legacy record quality, the same exposure to identifier discipline in the new domain. |
| T3 | Field Service Management, Maximo Mobile | Job plans, durations, crafts, shifts and whatever dispatch practice exists today. | One depot or one work type, with mid-shift change rules written down before configuration. | The existing dispatch habit runs faster and reaches more people, including the parts nobody defends. |
Cite the tier code in a scoping paper. T1 to T3 are stable and will not be renumbered.
Sequence
One application, on one asset class, chosen because its prerequisite already holds.
Nine applications waiting on the same data programme is a slower answer than one that reports inside a quarter. The order we argue for is set out in sequencing Monitor and Predict after Manage.
Table three
Five stages, whichever application you start with
Stage one is allowed to end in a no, which is why the answer arrives in weeks.
- 01
Readiness
Register quality, work coding and OT access tested against the application in mind, on one class.
Owner MaxIron with your data and reliability leads Typically 2 to 3 weeks
- 02
One scope
One application on one asset class, portfolio or building, small enough to settle the case in a quarter.
Owner Joint, signed by the sponsor defending it Typically 1 week to agree
- 03
Integration design
Into the OT estate or the back-office stack, with the approver named before build starts.
Owner MaxIron with your OT and integration owners Typically 3 to 6 weeks
- 04
Managed run
Live on our cloud, run by the team that already operates Manage, with runbooks and escalation paths handed over.
Owner MaxIron operations Typically Continuous
- 05
Sequence the next one
The next application chosen on the result of the last, with evidence behind the choice.
Owner Your sponsor, with our assessment Typically At the quarterly review
Also delivered
IBM industry solutions and add-ons we run today
Industry solutions
- Oil and Gas
- Operator rounds, certificates and context against the safety case.
- Utilities
- Compatible units, work design, network features and outage workflow.
- Civil Infrastructure
- Linear referencing, defect and closure planning for roads and bridges.
- Aviation
- Airworthiness and configuration against the airframe and engine record.
- Nuclear Power
- Work control and regulatory evidence calibrated to the licensing regime.
- Transportation
- Mileage, usage and modification control across rolling stock.
- Life Sciences
- Calibration, validation and audit traceability under FDA and EMA rules.
Add-ons
- Asset Configuration Manager
- As-designed, as-maintained and as-built configuration tracking.
- Scheduler and Optimization
- Graphical scheduling, resource levelling and constraint-based optimisation.
- Linear Asset Management
- Linear referencing for pipeline, cable, road and rail networks.
- Health, Safety and Environment
- Permits to work, incidents and hazardous materials on the work record.
- MRO Inventory Optimization
- Stock policy, forecasting and reorder points on Manage inventory.
- Maximo Spatial
- Geospatial context behind crew dispatch in distributed estates.
- Maximo for Service Providers
- Customer hierarchy, contract pricing and billing on Manage.
- ERP Connectors
- IBM-supported SAP and Oracle integration for items, orders and GL postings.
Licensed separately from Manage. Entitlement belongs in a licensing conversation with the numbers in front of us.
Scope of this page
Four boundaries we hold when we scope the suite
No suite-wide programme
We will not propose deploying the catalogue at once. One application, one class or one building, then the next decision on the result.
No proprietary models
Predict, Health and Visual Inspection use the model lifecycles that ship with MAS. We add scoping, data engineering, integration and operations.
No licensing advice dressed as architecture
AppPoints and entitlement belong in a licensing conversation with your figures on the table.
Nothing claimed that we do not operate
This page lists what we run today. The IBM catalogue is wider and it moves, so a missing capability is a scoping question.
The wider IBM MAS suite, frequently asked questions
- Where does the MAS suite go beyond Maximo Manage?
- Manage holds assets, work and inventory. Monitor, Predict, Health and Visual Inspection read those records and add operating signal, failure probability, scoring and image models. Renewables, Field Service Management, Real Estate and Facilities and Maximo Mobile extend the operating model into generation portfolios, dispatch, leases and the field.
- Which applications depend on a clean Manage foundation first?
- Monitor, Predict, Health and Visual Inspection inherit the state of the Manage records they read. Real Estate and Facilities and Renewables run as a standalone performance tool bring their own structures, so they can run alongside a Manage programme. The readiness assessment tests which case applies on your estate.
- Is this a separate platform from our Maximo environment?
- No. Every application on this page is part of IBM Maximo Application Suite, on the same Red Hat OpenShift estate, sharing user management and AppPoints with Manage. The same managed hosting and operations apply.
- Should we adopt the wider suite before Manage is stable?
- No. Predict learns from failure coding, Health ranks a register, Monitor binds tags to asset records, and each of those inherits whatever state Manage is in. Sequencing Monitor and Predict after Manage sets out the readiness checks we run.
- Does MaxIron deliver all of this today?
- Yes. We configure, integrate, host and operate these applications on the same managed cloud as Manage, with the same delivery and operations teams. Where an IBM industry solution or add-on is not listed on this page, ask in scoping.
Related capabilities
How the suite connects to your Maximo programme
Bring one asset class and the decision waiting on it.
Pick the row in table one closest to your operations meeting. We run the readiness assessment on the smallest slice of estate that could settle it, and say which application earns its licence first.
Bring this to the first call
- The row above that reads closest to your own situation
- One asset class, one portfolio or one building to test it against
- A Manage export for that slice: hierarchy, criticality, work history
- Which MAS applications you are already entitled to
- The decision or deadline this has to be ready for