The standing question for any operator who runs Maximo for the heavy industrial estate and an IWMS for the corporate real estate and facilities estate is whether to consolidate. IBM Maximo Real Estate and Facilities — the IWMS capability formerly known as TRIRIGA, now delivered on the MAS suite — makes that consolidation a real option for the first time. It is not always the right answer, and being honest about when it is and when it is not is more useful than the supplier pitch on either side.
The case for consolidation
The case for consolidating IWMS workloads onto MAS is strongest under three conditions, taken together.
The existing IWMS or CAFM tool is at end-of-life or end-of-contract, and the renewal conversation is open. Renewals are often the easiest moment in the platform lifecycle to make a strategic decision. If the renewal is two years out and quiet, the consolidation case is real but less urgent.
The Maximo footprint is healthy and well-operated. REF runs alongside Manage on MAS. If Manage itself is shaky — weak hierarchy, weak coding, low adoption — adding REF to the same platform compounds the existing problems rather than solving the IWMS one. Stabilise Manage first. The detail is in our services.
The operations team has the appetite and the capacity to absorb the IWMS workload. This is a real constraint. If the operations team that runs Manage today is already at the limit of what it can sustain, putting REF onto the same platform without reinforcing the team is asking for trouble. Consolidation reduces the number of platforms; it does not reduce the operating workload to zero.
Where these three are true, REF earns its licence over a stand-alone IWMS within a single budget cycle. One platform, one OpenShift estate, one operations team, one upgrade cadence, one set of integrations to maintain.
The case against — for a particular kind of operator
There is a class of operator for whom REF is not the answer, and we will say so.
Where the corporate real estate operating model is genuinely customer-facing in a way that asset management is not — for example, a commercial real estate platform with tenant-facing service portals as a first-class artefact, complex revenue recognition across leases, and a property-management ecosystem that REF does not naturally cover — the dedicated commercial real estate platforms are usually the right answer. REF does the IWMS workflows well; it is not a customer-facing commercial real estate platform.
Where the facilities estate is genuinely tiny relative to the industrial estate, the consolidation savings do not show up. The cost of running REF alongside Manage is not zero, and it has to be earned back somewhere. A dozen leased offices and a small PPM regime do not earn it back.
Where the operator’s TRIRIGA estate is so deeply customised that the migration cost would dwarf the consolidation savings for years, the right answer may be to ride the existing platform a while longer and revisit at the next inflection. Migration cost is a real number and we will quote it honestly.
The two integration points that decide the project
Where the consolidation goes ahead, two integration points decide whether the project is comfortable or painful.
Lease accounting and the finance system. REF carries the IFRS 16 / ASC 842 lease accounting capability that the IWMS market has been built around. The journals it produces have to land cleanly in the operator’s finance system, on the right cadence, with the right control points. Where this integration is well-scoped — chart of accounts mapped, entity structure understood, audit trail explicit — the lease accounting capability is one of REF’s strongest cards. Where it is hand-waved, the project burns a quarter on it.
Sustainability and ESG reporting. REF captures energy, water, waste and emissions data against the estate, supporting GRESB, CDP and similar frameworks. Where the operator already has an ESG reporting framework with named recipients and named cadences, REF feeds it cleanly. Where the operator is hoping REF will define the framework for them, the project becomes an ESG strategy exercise wearing an IWMS deployment costume. We try to head this off early.
These two are the integration points we ask about in the first conversation. The answers tend to predict the comfort of the project more accurately than any of the technical scoping.
What about TRIRIGA specifically
For operators with an existing IBM TRIRIGA footprint, the migration to REF on MAS is not a literal lift-and-shift. The capabilities are the same lineage, but the platform is different and the right move is usually a deliberate redesign rather than a wholesale port. Configurations and reports that have accreted over years can almost always be simplified on the way across; the migration is a good moment to retire the customisations that nobody uses and to standardise on the patterns the new platform is built around.
We have a view, and the practical guidance lives in conversation rather than in a marketing line.
Closing position
REF earns its licence over a stand-alone IWMS where the existing tool is at a renewal moment, where Manage is healthy enough to be the platform companion, and where the operations team has the capacity to absorb the workload. It is not the answer for every operator and we will say so where it is not. Where it is the answer, the lease accounting integration and the ESG reporting integration are the two scope items that decide whether the project is comfortable.
For the broader implementation pattern, see IBM Maximo Real Estate and Facilities — how we deliver it and the pillar guide for buyers.