TRIRIGA to MAS / MREF
September 2027 is closer than it looks.
Every TRIRIGA practice and internal team has the same year on the calendar. Forge makes the squeeze workable, ship faster on TRIRIGA right now, then validate parity as workflows move to IBM Maximo Real Estate and Facilities on Maximo Application Suite.
The deadlines
Two dates worth pinning to the wall.
28 January 2026
TRIRIGA SaaS new orders ended
IBM stopped accepting new orders for TRIRIGA SaaS. Existing customers continue, but the renewal calendar now points at MREF on MAS.
30 September 2027
TRIRIGA support concludes
All versions of IBM TRIRIGA and IBM TRIRIGA Application Suite reach end of support. The designated upgrade path is Maximo Real Estate and Facilities 9.x on Maximo Application Suite.
Source: IBM lifecycle announcements for TRIRIGA and TAS. Confirm specifics for your own contract with your IBM account team or BP.
How Forge fits the migration
The same servlet shape, on TRIRIGA today and MREF tomorrow.
The product was designed before MAS 9.1 shipped, with the migration explicitly in mind. The same servlet runs on TRIRIGA Platform 3.x to 5.x and TAS 11.x today, and is in active validation on Maximo Application Suite 9.1+ for MREF. That means the metadata graph you build now keeps its shape after the cutover.
Ship faster on existing TRIRIGA
Your team is fixing bugs, building reports, and shipping change requests against TRIRIGA today. Forge makes those investigations minutes instead of hours, on the platform you already run, with no migration prerequisite.
Map what you actually use
Use the metadata graph to enumerate every workflow, business object, form, and configuration that your TRIRIGA actually executes. Surface the ones that drive operations vs the ones that exist but never run. The migration scope shrinks before you cost it.
Validate parity on MREF
When you stand up MREF on MAS 9.1+, the same servlet shape and the same metadata graph give you side-by-side validation. Compare a workflow's behaviour on TRIRIGA vs its behaviour on MREF. Drift becomes visible, not theoretical.
Across TRIRIGA, TAS, and MREF
One shape. Three platforms. Same toolchain.
IBM TRIRIGA
Platform 3.x to 5.x
Classic on-premises TRIRIGA. Fully supported. The platform most existing practices and internal teams run today.
IBM TAS
TAS 11.x on OpenShift
Containerised TRIRIGA Application Suite. Fully supported. Many practices' bridge platform between classic TRIRIGA and MAS.
IBM MREF
MAS 9.1+ (validating)
IBM Maximo Real Estate and Facilities on Maximo Application Suite. Compatibility being validated by our team against MAS 9.1+ environments.
What you can do this quarter
Practical migration prep, no MAS environment required.
Inventory what you actually run
Use the metadata graph to enumerate every workflow, BO, form, and configuration on each environment. Tag what executes vs what is dead weight. The migration scope is usually 40-60% smaller than the licence inventory suggests.
Snapshot the working baseline
Capture today's workflow versions and BO configurations. After cutover, compare against the MREF state to flag drift in minutes instead of weeks.
Fix the top 20 chronic issues
Use AI-assisted diagnosis to clear the backlog of TRIRIGA quirks before they migrate. Don't take the bugs with you. Don't migrate the workarounds.
Get developers fluent in MREF early
Same MCP shape, same query patterns, same diagnostics flow. The team's Forge muscle memory transfers directly to MREF the moment the validation completes.
- No MAS environment required to start. Run on your existing TRIRIGA today.
- Same servlet, same MCP shape, same query patterns when you reach MREF.
- Validation against MAS 9.1+ in active progress. Customers in early access programmes can shape priorities.
Plan your TRIRIGA-to-MREF move with the tooling already in place.
We will look at your TRIRIGA estate, where MREF lands in your roadmap, and where AI tooling collapses the work between now and cutover. 30 minutes, no slides.