MAS suite
The rest of MAS, delivered by the team that runs your Maximo
Manage is still where most asset-intensive operators get the biggest day-one return, and we have built MaxIron around delivering Manage well. For clients ready to go further, we already deliver and operate the analytics and connectivity layer (Monitor, Predict, Health, Visual Inspection, IoT) and the application layer (Renewables, Field Service Management, Real Estate and Facilities, Mobile), in our cloud, today.
The IBM Maximo Application Suite is more than Manage. The conversation beyond Manage tends to split into two directions, and on this page they sit side by side. There is the analytics and connectivity layer — Monitor, Predict, Health, Visual Inspection and the IoT layer underneath them — that turns operating data into work. And there are the specialist solutions — Renewables for wind, solar and battery storage, Field Service Management for mobile workforces, Real Estate and Facilities for buildings and leases, and Maximo Mobile for the field — that extend the operating model into adjacent asset domains. Beyond those, IBM ships a wider catalogue of industry solutions (Manage configured for an asset domain) and add-ons (capabilities that bolt onto Manage); we deliver and operate those too, and they are listed further down this page.
Most of our clients are still buying Manage, and that is the right call. Our Manage services are where the bulk of value lands today. The page you are on now is for the conversation that comes next: when Manage is in good shape and the executive team starts asking what else the suite can do, what AI is going to mean for operations, and which capabilities to invest in first.
What we already deliver and run today
- Implementation and configuration of all components and applications listed below on the same Red Hat OpenShift estate as Manage
- Integration with SCADA, historians, edge gateways, OEM portals, ERP, finance, CRM and the OT/IT boundary, in production
- Managed hosting of the full suite on our cloud, with the same operations platform that runs our Manage estate
- Run and support alongside Manage, with a single team accountable for the whole platform
Sequencing matters more than scope
Treating the suite as one big bang rarely ends well. Predict learns wrong lessons from thin failure history. Health scoring is meaningless against an incomplete asset register. Monitor surfaces anomalies on equipment Manage does not know about. Renewables struggles when the OEM portal is still authoritative. FSM amplifies whatever the dispatcher already does, including the broken parts. We argue, on every engagement, for sequencing after Manage is stable enough to be the system of truth. The detailed argument lives in sequencing Monitor and Predict after Manage.
Group one
AI, analytics and connectivity
The components that turn operating data into work — they sit on top of Manage and get sharper as the asset and work data underneath them gets cleaner.
Live operating data into the asset system
IBM Maximo Monitor
Bring SCADA, historian and edge signals into MAS so the people who run the assets see what is happening in time to act, and so Manage holds the operating context, not a parallel spreadsheet.
How we deliver it →
Failure-probability where the data supports it
IBM Maximo Predict
Apply analytics to the equipment where failure history is rich enough to learn from, and feed the output into the work plans your planners and reliability engineers already trust.
How we deliver it →
Asset health scoring and capex prioritisation
IBM Maximo Health
Score the estate against criticality, condition and consequence, and use it to defend the maintenance plan, target capital and produce the evidence ISO 55001 auditors expect.
How we deliver it →
Image and video models in safety-critical inspections
IBM Maximo Visual Inspection
Make routine and safety-critical inspections faster and more consistent, with a defensible evidence trail that survives an audit and a change of inspector.
How we deliver it →
The layer underneath Monitor and Predict
IoT and OT connectivity
Design and operate the SCADA, historian, edge and OT/IT connectivity that Monitor and Predict need, without breaking the OT team or the cybersecurity boundary.
How we deliver it →
Group two
Industry and workflow solutions
The MAS solutions that extend the Manage operating model into adjacent asset domains and into the field — same platform, same team, different workflows.
Wind, solar and battery storage on Maximo
IBM Maximo Renewables
Run wind farms, solar arrays and battery storage as one operating portfolio: SCADA and OEM portal ingest, performance and availability analytics, and the work it generates lands directly in Maximo Manage.
How we deliver it →
The Manage backbone, extended to the back of the truck
IBM Maximo Field Service Management
Maximo Mobile (online and offline), Scheduler, Optimizer, Spatial and Collaborate — one asset record from plan to dispatch to close-out, without a parallel field service tool.
How we deliver it →
IWMS on the same platform as the plant
IBM Maximo Real Estate and Facilities
The IWMS capability formerly known as TRIRIGA, now on MAS: real estate and lease admin, capital projects, space planning, facilities operations and ESG reporting.
How we deliver it →
Where Maximo lives or dies for the field
IBM Maximo Mobile
The native MAS mobile app for technicians, inspectors and operators. We design and roll it out offline-first, around how the trade actually works, with adoption that holds after go-live.
How we deliver it →
Group three
The wider MAS catalogue we deliver
Beyond the headline applications and analytics, IBM ships a catalogue of industry solutions (Manage configured for a specific asset domain) and add-ons (capabilities that bolt onto Manage). We deliver, integrate and operate these on the same managed cloud as everything above. They do not have their own pages here on purpose — the right conversation about each is in scoping, not in marketing copy.
Industry solutions
Manage configured for an asset domain
IBM's industry solutions are pre-built configurations of Manage calibrated to a specific asset domain — data model, work types, regulatory shape and inspection regime. We deliver and operate the following.
- Maximo for Oil and Gas. The IBM industry solution for upstream and midstream operators — operator rounds, certificates, condition for monitoring, location/operating context configured against the safety case.
- Maximo for Utilities. The IBM industry solution for gas, electricity and water networks — compatible units, work design, network features, crew, mobile and outage workflow on the Manage backbone.
- Maximo for Civil Infrastructure. The IBM industry solution for road, rail and bridge owners — linear referencing, defect and closure planning, inspection regimes that match the asset shape.
- Maximo for Aviation. The IBM industry solution for airline and MRO operators — airworthiness, configuration, regulatory traceability against the airframe and engine record.
- Maximo for Nuclear Power. The IBM industry solution for nuclear operators — work control, configuration management and regulatory evidence calibrated to the licensing regime.
- Maximo for Transportation. The IBM industry solution for rail and fleet operators — configuration management, mileage/usage tracking, modification control across the rolling stock.
- Maximo for Life Sciences. The IBM industry solution for regulated life-sciences operators — calibration, validation and audit traceability under FDA / EMA expectations.
Add-ons
Capabilities that bolt onto Manage
IBM's MAS add-ons are licensed separately and extend Manage with capabilities most operators eventually need. We deliver and operate the following.
- Asset Configuration Manager (ACM). Configuration-managed assets with as-designed / as-maintained / as-built tracking — heavy on aerospace, defence and nuclear estates.
- Maximo Spatial. Geospatial context against the asset and work record. Underpins crew dispatch in distributed estates and is part of the FSM deployment pattern.
- Maximo Scheduler and Scheduler Optimization. Graphical scheduling, resource levelling, capacity planning and constraint-based optimisation. The planning backbone behind FSM.
- Maximo Linear Asset Management. Linear referencing for road, rail, pipeline and cable networks. The data model that makes Civil Infrastructure work properly.
- Maximo Health, Safety and Environment Manager (HSE). Permits to work, incident management, hazardous materials and audit / compliance workflows tied to the asset and work record.
- Maximo MRO Inventory Optimization. Stock policy, demand forecasting and reorder optimisation on top of Manage inventory — typically pays back inside one stocking cycle on a heavy estate.
- Maximo for Service Providers. Multi-customer service-provider model: customer hierarchy, contract pricing, billing and customer-facing service workflows on Manage.
- ERP Connector for SAP. IBM-supported SAP ERP integration: items, vendors, POs, receipts, invoices and GL postings between SAP and Manage.
- ERP Connector for Oracle. IBM-supported Oracle ERP integration: items, vendors, POs, receipts, invoices and GL postings between Oracle and Manage.
If the relevant solution or add-on is not on this page, ask. The catalogue moves and we deliberately keep this page to the ones we run today.
Future-readiness, in the present tense
AI is going to pull more of the asset estate into these capabilities
Boards are being told the asset operating model is about to change. Some of that is hype. A lot of it is not. The MAS suite is where IBM concentrates the parts of that change that are real for asset-intensive operators: live operating data, predictive analytics, health scoring, vision models, and a mobile front door for the field. When that conversation lands at your door, we will already have had it on other estates.
Related capabilities
How the suite connects to your existing Maximo programme
MaxIron products
MaxIron products that strengthen MAS suite operations
Frequently asked questions
- Where does the MAS suite go beyond Maximo Manage?
- Manage is the system of record for assets, work and inventory. The wider MAS suite splits into two directions on top of it. The analytics and connectivity layer is Monitor (live operating data and anomaly detection), Predict (failure-probability analytics), Health (asset health scoring and prioritisation), Visual Inspection (image and video models for inspection) and the IoT/OT connectivity underneath. The application layer is Renewables (wind, solar and battery storage), Field Service Management (mobile workforce and dispatch), Real Estate and Facilities (the IWMS formerly known as TRIRIGA) and Maximo Mobile.
- Does MaxIron actually deliver all of this today?
- Yes. We design, configure, integrate, host and run these MAS components and applications for clients today. They sit on the same managed cloud platform we use for Manage, and the same delivery and operations teams own them.
- Should we adopt the wider suite before Manage is stable?
- No. Predict learns wrong lessons from poor failure coding. Health scoring is meaningless against an incomplete asset register. Monitor surfaces anomalies on equipment that does not exist in the CMMS. Renewables struggles when the OEM portal is still authoritative. FSM amplifies whatever the dispatcher already does. Mobile rollouts amplify whatever the desktop already does, including the broken parts. Stabilise Manage first, then sequence the rest. Sequence Monitor and Predict after Manage sets out the readiness checks we use.
- Is this a separate platform from our Maximo environment?
- No. Every component and application listed above is part of the same IBM Maximo Application Suite. They run on the same Red Hat OpenShift estate, share user management and AppPoints, and consume from and feed into Manage. The same managed hosting and operations apply.
- Where does AI fit in this picture?
- Predict, Health, Visual Inspection and the Renewables analytics already use models built into MAS. The honest position is that AI will pull more of the asset operating model into these components over the next several years. We are positioned for that direction without claiming proprietary IP we do not have.
- What does an engagement on the wider suite typically look like?
- A short readiness assessment against Manage, a focused scope on the component or application that earns its licence first (often Monitor or Health on the analytics side, FSM or Renewables on the application side), an integration plan into the OT estate or the back-office stack as appropriate, and a managed run-state on our cloud. Then sequencing the next one based on results, not roadmap.