MAS suite
Implementation and operation across IBM Maximo Application Suite
MaxIron configures and integrates the applications, hosts the platform and operates IBM Maximo Application Suite alongside Manage. We start with one business decision and one asset class, establish the data and integration prerequisites, then support the live application through the same operations team as Manage.
Application choice
Match the operational requirement to an IBM capability
The operating decision identifies the application; the prerequisite determines whether the first scope can produce a useful result.
Monitor binds SCADA, historian and edge signal to asset records and opens anomalies against them.
How we deliver Monitor →Operating context
Operating data sits in the historian and never reaches the planner who could act on it.
Planning consideration
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 →Operating context
Reliability teams need failure estimates to inform intervention planning.
Planning consideration
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 →Operating context
A capital submission, a maintenance budget or an ISO 55001 audit has to be defended.
Planning consideration
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 →Operating context
Inspection findings vary between inspectors and the volume keeps rising.
Planning consideration
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 →Operating context
Plant data access requires an agreed OT security boundary and approved data flows.
Planning consideration
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 →Operating context
Wind, solar or storage assets from several manufacturers report in several portals.
Planning consideration
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 →Operating context
The dispatcher spends the shift moving jobs rather than handling exceptions.
Planning consideration
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 →Operating context
Lease dates, space data and building requests live in spreadsheets.
Planning consideration
Reusing plant work types for facilities requests, which loses the space hierarchy.
Maximo Mobile supports field capture and offline work against Manage records.
How we deliver Mobile →Operating context
The field still works from paper or from a desktop screen in the mess room.
Planning consideration
Shipping every work type at once instead of the two the trade uses daily.
Delivery prerequisites
Data and process prerequisites determine the first scope
Group by what each application depends on. That decides what starts this year and what waits for data work.
| Ref | Applications | Required data and process | Initial scope | Dependency to resolve |
|---|---|---|---|---|
| T1 | Monitor, Predict, Health, Visual Inspection | Mapped asset identifiers and the inputs for the chosen application: signals, scoring factors, failure history or labelled images. Manage integration adds its record and workflow dependencies. | Readiness assessment on one asset class, then remediate that class alone. | Asset identity and failure coding must support traceable analysis before operational acceptance. |
| 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. | Job durations, resource availability and dispatch rules need validation with the field team. |
T1 to T3 provide stable references for a scoping paper.
Delivery responsibilities
IBM capability, MaxIron implementation and customer decisions
The delivery scope separates product functionality from configuration work and the operational authority that remains with your organisation.
| Ref | IBM capability | MaxIron implementation | Customer decision and prerequisite |
|---|---|---|---|
| D1 | Monitor and condition analytics | Bind historian or edge signals to asset identifiers; configure thresholds, anomaly review and the Manage work path. | OT security approves the data path; the engineer accepts the condition and the planner authorises work. Asset and tag identifiers must align. |
| D2 | Predict and Health | Prepare failure history, configure scoring or model evaluation, and test the output with reliability teams. | Asset management agrees criticality and consequence; engineering approves intervention. History and an appropriate asset population support evaluation. |
| D3 | Visual Inspection | Agree defect classes, prepare labelled images and validate precision and recall in the inspection workflow. | The competent inspector confirms findings and return-to-service decisions. Representative images and an approved defect dictionary precede training. |
| D4 | Mobile and field service capabilities | Configure work types, offline scope, dispatch rules and the supporting interfaces. | Operations agrees access windows and dispatch authority; field teams validate job plans, skills and durations. |
For programme evidence, review the UK ferry operator MAS programme and airport Manage and Mobile programme. These references describe their own delivered scope.
Delivery and operation
Five stages, whichever application you start with
Each stage has a named owner and acceptance evidence. Indicative timing below is confirmed against data readiness, access and the chosen application during scoping.
- 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
Industry solutions and add-ons to assess during scoping
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.
Entitlement, deployment options and application availability are checked against your IBM agreement and MAS version. IBM publishes the Maximo capability overview and Real Estate and Facilities options.
What we cover
Four boundaries we hold when we scope the suite
Adoption proceeds in bounded phases
We propose one application on an agreed asset class, portfolio or building. The operational result and acceptance evidence determine the next phase.
IBM capability with MaxIron delivery
IBM supplies the application capabilities. MaxIron scopes the use case, prepares data, configures integration and supports the agreed model lifecycle and operations.
Entitlement is confirmed before deployment
AppPoints and entitlement belong in a licensing conversation with your figures on the table.
Application scope is confirmed for your estate
The proposed scope identifies the application, MAS version, deployment model and support responsibilities. Additional IBM capabilities are reviewed during scoping.
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?
- The prerequisite depends on the use case: condition monitoring needs mapped asset identifiers and reliable signals; Predict needs usable history; Health needs agreed scoring inputs; Visual Inspection needs representative labelled images. Manage readiness matters where the workflow reads its records or writes accepted work into it.
- Is this a separate platform from our Maximo environment?
- IBM offers client-managed and SaaS deployment options across the Maximo portfolio. The application, release and licence agreement determine the deployment and integration requirements. We confirm the architecture and operating boundary against your existing Manage environment during the readiness assessment.
- Should we adopt the wider suite before Manage is stable?
- Choose a scope whose required data, access and decision authority are ready. Where that scope relies on Manage work history or asset records, remediate those dependencies first. Sequencing Monitor and Predict after Manage describes the delivery checks.
- Does MaxIron deliver all of this today?
- MaxIron provides implementation, integration and operating services around IBM Maximo. The proposal names the applications, deployment responsibilities and relevant delivery experience for your chosen scope; published client work describes the programmes available for review.
Bring one asset class and the decision waiting on it.
We run the readiness assessment on the smallest slice of estate that could settle the decision, then identify the application and prerequisites for a responsible first phase.
Bring this to the first call
- The operating decision that needs better asset evidence
- 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