TRIRIGA, MREF and your next platform decision
Moving from TRIRIGA to MREF? Know your options.
IBM's route leads to Maximo Real Estate and Facilities (MREF), within Maximo Application Suite (MAS). Compare a support bridge, the IBM route, and staged replacement using evidence about the estate you run.
Your options
Compare the route, the cost, and the responsibility.
The bridge protects continuity while a destination is selected and delivered. Both long-term routes need evidence of capability, cost, and operating fit.
01 / A temporary bridge
Buy time on TRIRIGA
Use eligible paid support and current hosting while you select, fund, and deliver the next step.
Before committing
Confirm the support scope, hosting continuity, expiry dates, and transition budget. Give the bridge a purpose and an end date.
02 / The IBM route
Move to MREF within MAS
Follow IBM's designated route to Maximo Real Estate and Facilities, with a suitable customer-managed or IBM-managed deployment.
Before committing
Validate the target architecture, licence entitlement, customisations, integration work, and migration and test scope.
03 / An alternative destination
Replace capabilities in stages
Move the business capabilities you need to another platform. Plan coexistence and controlled cutover around the services that must keep running.
Before committing
Prove functional fit, data and integration handling, operating costs, recovery, and exit before expanding the commitment.
What changes with MREF
Plan the operating model alongside the application.
Hosting and operations
Customer-managed MREF runs on Red Hat OpenShift. IBM-managed deployment changes who operates the platform. Compare infrastructure, skills, monitoring, recovery, and responsibility.
IBM deployment optionsLicensing and users
MAS manages AppPoints, user access, and entitlements at suite level. Review your actual licence terms and user migration requirements alongside the technical plan.
IBM: what changes in MREFMigration and application upgrades
Moving from the TRIRIGA platform to MREF and updating the business application are distinct pieces of work. Agree the source, target, sequence, and validation for each.
IBM upgrade guidanceSupport and transition dates
Put the right dates in your plan.
The dates have different meanings. Check your product versions and purchased terms with IBM. Sources reviewed 6 September 2026.
30 September 2027
Base support changes
IBM ends regular maintenance fixes and base support for TRIRIGA/TAS Application 11.6, Platform 5.0, and corresponding listed components.
IBM transition terms30 April 2029
MAS dual support ends
Eligible trade-up customers must plan within the dual-support terms. IBM also requires TRIRIGA/TAS use to stop once the technical migration to MAS Real Estate and Facilities is complete.
IBM dual-support terms30 September 2032
Paid coverage has a limit
The Platform 5.0 lifecycle lists this as the end of Extended/Sustained coverage availability. Later Sustained Support covers usage and existing fixes, with narrower coverage than base support. Confirm eligibility and price.
IBM Platform 5.0 lifecycleBuild a comparable business case
Compare three-year cost on the same basis.
Use the same business scope, service levels, and transition period for every option. A hosting estimate alone does not show the cost of running and changing the service.
| Cost area | Include | Ask for |
|---|---|---|
| Software | Licences, AppPoints or other usage metrics, growth, and non-production rights. | Current quotes and entitlement terms |
| Hosting and service | Infrastructure, database, platform operations, monitoring, backup, recovery, and support. | Sizing and agreed service responsibilities |
| Migration and testing | Configuration, data, integrations, user migration, rehearsal, testing, and internal team time. | A delivery plan with explicit assumptions |
| Overlap | Paid support, dual running, parallel service, and the length of the transition. | Bridge terms and a funded timeline |
| Continuity and exit | Data export, decommissioning, transition assistance, and supplier continuity arrangements. | Recovery evidence and an agreed exit plan |
This is a comparison framework. Obtain current supplier quotes and confirm scope and commercial terms before making a cost or savings claim.
Where FORGE helps
Establish the facts about your current estate.
Use source-estate evidence to inform requirements, estimates, and the verification plan, whichever destination is under consideration.
Inventory the current estate
Identify the configuration, customisations, and integrations relevant to the decision, with source and environment context.
Trace the dependencies
Find related fields, workflows, forms, queries, and integration touchpoints. Record gaps that need specialist investigation.
Define what must be verified
Use the findings to agree test candidates, critical journeys, and the evidence the programme needs before accepting a target.
A scoped readiness pilot
Test one migration-readiness question.
Setup and a four-week pilot: one outcome, one non-production environment, up to three working sessions, and an evidence pack. Agree the tools and success criteria before access.
A full options assessment, replacement programme, or migration is separately scoped and quoted. MREF target compatibility remains under validation.
Review the pilot terms and included scopeFor your internal discussion
Take the options to your decision-makers.
Our executive briefing explains the wider IBM platform transition, the three routes, and the cost, capability, contract, and continuity questions to put to each supplier.
IBM platform transition: current position and options
12 slides · PowerPoint · 64 KB · 3 September 2026
Download the executive briefingNo email required. Current IBM terms take precedence.
MREF questions
Before you commit to a route.
Will TRIRIGA stop working in September 2027?
The published milestone changes support for the named versions; it is not a remote switch-off date. Continued use, paid coverage, and hosting still depend on your licence, support, and service terms. Confirm those terms while planning the destination.
Check IBM's lifecycle noticeDo we have to operate OpenShift ourselves?
Customer-managed MAS uses OpenShift. IBM also offers managed deployment options. Compare the supported arrangement for your environment and the responsibilities that remain with your organisation, including application configuration, data, users, and integrations.
Compare IBM deployment optionsHow long will the move take?
Your source version, configuration, integrations, target, and programme scope determine the plan. IBM notes that complex enterprise application upgrades can take 12 to 18 months. That is application-upgrade guidance, not a standard duration for every MREF platform migration.
Read IBM's upgrade planning guidanceCan FORGE carry out the migration for us?
FORGE provides estate intelligence and scoped, governed tooling. Its current migration offer starts with source-estate evidence and readiness planning. MREF compatibility validation is in progress; automatic migration, workflow parity, and general target support are not promised. Execution and target verification require separately agreed scope and tested compatibility.
Does the standard setup and pilot cover a complete options assessment or migration?
It covers one agreed FORGE outcome in one non-production environment over four weeks, with up to three working sessions and an evidence pack. A full options assessment, IBM sizing or licensing exercise, application replacement, and migration delivery are separately scoped and quoted.
Bring the decision you need to make.
Tell us your current TRIRIGA version, the routes you are considering, and your decision date. We can establish which evidence is missing and scope a useful next step.