Why Maximo 9.x is on every CIO's agenda
IBM Maximo 7.6 end-of-support is no longer a distant risk. For asset-intensive organisations running maintenance, reliability and capital planning on Maximo 7.6, the question has shifted from whether to upgrade to how fast you can get to Maximo Application Suite (MAS) 9.x without disrupting operations.
MAS 9 is not a patch release. It is a re-platform onto Red Hat OpenShift, with new licensing, new integration patterns, and a different operational model for upgrades, monitoring and mobile. Programmes that treat it as a technical version bump routinely underestimate cost, duration and business change.
Valueztech has been involved in three recent programmes that illustrate the full upgrade journey, from the board paper to production cutover.
Programme 1: Scoping and business case
Before any environment is built, leadership needs a defensible answer to four questions:
- What is the target architecture: on-prem OpenShift, AWS ROSA, IBM Cloud, or managed SaaS?
- Which customisations, integrations and reports must move, retire or be rebuilt?
- What is the realistic cost, risk and timeline?
- What business outcomes justify the investment?
In a recent scoping and business case engagement, Valueztech ran a structured readiness assessment across the client's Maximo 7.6 estate: custom Java and automation scripts, BIRT reports, MIF and REST integrations, security groups, mobile usage, and ERP touchpoints. The deliverable was a board-ready business case with architecture options, a rationalisation register (keep / refactor / retire), a phased roadmap, and TCO bands for each hosting model.
Lesson: The business case phase pays for itself when it prevents a big-bang migration that the organisation cannot absorb. Scoping should finish with an agreed target MAS version, cutover strategy and test approach, not just a list of technical gaps.
Programme 2: Maximo 7.6 to 8.9 for a major chocolate manufacturer
Not every organisation jumps straight to MAS 9 in one step. A major chocolate manufacturing client needed to exit an unsupported 7.6 footprint while stabilising integrations to production and supply-chain systems. Valueztech supported a 7.6 to Maximo 8.9 upgrade programme as an intermediate milestone on the path to MAS.
Key workstreams included:
| Workstream | Focus |
|---|---|
| Customisation review | Automation scripts, escalations and workflows exercised against 8.9 behaviour |
| Integration regression | ERP and shop-floor interfaces retested after platform changes |
| Data and security | Organisation structure, storerooms, labour and craft migrations validated |
| Testing | Functional UAT plus MaxTAF regression packs for repeatable release evidence |
| Cutover | Phased go-live with hypercare and rollback criteria agreed upfront |
Manufacturing environments add complexity: production lines do not pause for a maintenance system upgrade. Parallel running, clear freeze windows and shop-floor communication were as important as the technical migration scripts.
Lesson: An 8.9 stepping stone can de-risk a later MAS 9 move, but only if customisations are rationalised now, not copied forward twice. Every script carried from 7.6 to 8.9 without review becomes debt on the MAS programme.
Programme 3: Maximo 7.6 to MAS 9 for a Victorian water utility
A Victorian water utility programme moved from Maximo 7.6 to Maximo Application Suite 9, the full re-platforming journey utilities across Australia are now planning.
This engagement covered:
- Target architecture on OpenShift with integration to GIS, SCADA-adjacent systems and corporate ERP
- MAS Manage configuration aligned to water network and treatment plant asset hierarchies
- Maximo Mobile for field crews working across regional service areas with offline-first execution
- Data migration from 7.6 asset, location, PM and work-order history with reconciliation sign-off
- Regression testing with MaxTAF automation for core work-management and integration scenarios
- Training and hypercare so planners and supervisors were productive in the first month after cutover
Water utilities face regulatory reliability expectations, audit-grade work history, and geographically distributed teams. Upgrade success was measured in continuity of service: work orders still dispatched, compliance inspections still recorded, and ERP financial flows uninterrupted.
Lesson: Utility upgrades succeed when mobile, integration and reporting are in scope from day one, not bolted on after go-live. MAS 9 native capabilities are only valuable once the foundation data and integrations are clean.
What these three programmes have in common
Despite different industries and target versions, the same patterns appeared in every engagement Valueztech led or supported:
- Start with outcomes, not versions. Reduced downtime, audit-ready work history, mobile adoption and ERP alignment are strategies.
- Rationalise before you migrate. Duplicate assets, broken hierarchies and unused customisations multiply test effort.
- Test like you mean it. MaxTAF regression automation for Maximo 7.6 through MAS 9.x compresses test cycles.
- Plan cutover as an operational event. Freeze windows, rollback criteria and hypercare staffed by people who know your Maximo configuration.
- Use the Innova delivery method. Prototype-proven backlogs kept stakeholders seeing tested software every sprint.
Planning your upgrade?
If Maximo 7.6 end-of-support is on your risk register, start with a MAS readiness assessment and a business case your board can approve. Valueztech delivers scoping, 7.6-to-8.9 upgrades, and full 7.6-to-MAS-9 programmes for utilities, energy, manufacturing and infrastructure operators across Australia.
Book a discovery call or explore our IBM Maximo upgrade services and IBM Maximo resource hub.