IBM Maximo Real Estate and Facilities (MREF), formerly IBM TRIRIGA
Run, support, and evolve TRIRIGA and MREF.
FORGE by AJAEX equips your AI with the tools to investigate support issues, diagnose server-side Java, prepare proposals and designs, and implement and release approved changes across your TRIRIGA and MREF instances, on both sides of the move.
Setup, pilot, and subscription pricing are agreed for your scope. Contact AJAEX for a proposal.
Discuss a pilotFollow the evidence
What depends on this field?
Trace the references. Build the test scope.
- Workflow
- Reads or sets the value
- field_where_used
- Form
- Shows or edits the field
- form_audit
- Query
- Filters or reports on it
- where_used
- Integration
- Carries it to other systems
- integration_object
field_impact ranks the change risk; blast_radius covers a whole business object.
81 MCP tools across metadata, records, runtime and governed change. Registry as of 2 October 2026. Tool names shown without their tririga_ prefix.
Runs three ways
Illustrative relationship map. Not a live customer result.
Works with TRIRIGA and MREF
Traceable dependency evidence
Your team stays in control
IBM Silver Business Partner
AJAEX LTD
Your AI, equipped for TRIRIGA and MREF
An ongoing support and delivery partner.
Take on the work of running TRIRIGA and MREF from end to end: investigate incidents, understand server behaviour, propose changes, prepare designs, implement approved work, and promote and verify the release across connected instances.
Day-to-day support and incident investigation
Server-side Java investigations
Change proposals, FDDs, and TDDs
Implementation alongside your team
Packaging, deployment, and verification
Start with one support or delivery outcome, then expand the agreed scope. Your AI client handles reasoning and document preparation; FORGE provides specialist TRIRIGA evidence and enabled actions. Your team approves designs and production changes.
From question to evidence
Less archaeology.
More understanding.
A routine change can mean hours moving between Data Modeler, Workflow Builder, forms, and queries, then waiting for the person who knows the history. FORGE gives your team another way into that investigation: ask the question and follow the evidence from the agreed environment.
Email the requester when a request is submitted
39 seconds · With captionsThe workflow was already there.
Asked to create a notification, FORGE checked the instance and found that TRIRIGA already supplies the workflow.
The next step: verify the existing setup and switch it on, then customise it if needed.
Recorded investigation. Your own instance determines what applies.
Read the video transcript
Very often people don't really know how to do notifications in TRIRIGA. I would like to create an email notification to the requester of a service request when it's raised and submitted.
Already ships this behaviour. Oh, there you go, we didn't know that. You're mostly just verify and switch it on to customise it, what already exists in your instance.
Associate the Requested For person to the helper, and that's who gets notified.
Here it took 2 minutes 14 to produce a really accurate understanding of what it should do, what's already there.
One familiar change
An approval threshold changes. What needs checking?
The useful result is a reviewable account of what references the field, where that evidence came from, and what your team should investigate or test next.
FORGE helps trace the dependencies. Your specialists use that evidence to agree the change and regression scope.
- Workflow conditions
- Which approval routes reference the field? Check requests on either side of the new threshold.
- Forms and queries
- Where is the value displayed, edited, or filtered? Identify the screens and worklists to test.
- Integration mappings
- Which connected systems use the value? Confirm the mapping and expected downstream result.
Each finding needs a source and a named environment. Missing access or evidence stays visible for follow-up. Actual relationships and tests depend on the inspected estate; this is not a customer result.
Worked examples
Real questions, answered from the system itself.
Three more short clips in which AJAEX puts everyday configuration questions to our MCP layer, which reads a TRIRIGA instance's own metadata. Timings are as measured in each clip.
Worked out in 2m 17s
A different SLA at each location
One customer, one service, two locations, and a different SLA at each. The answer: one service agreement, one service line per location with its own respond and due terms, and the SAM records that come out of it when the contract is activated.
Worked example
Map a work task's org stamp from the responsible org
Map a work task's organisation stamp from the responsible organisation with two new workflows and one edit.
Transcript
Show me what it would take to adjust this to map the org stamping from the responsible organization on that work task.
The change that would be required: two new workflows, one edit. On the associate organization, set customer org from responsible org.
It's called Cloud Login
Add an IdP in TRIRIGA without turning on SSO
TRIRIGA 5.0.7 supports adding an identity provider while keeping SSO=N, under Tools, System Setup, Integration, OAuth Settings. For teams moving to IBM MREF, that means several identity providers can sit in one system.
The answers come from a TRIRIGA instance through the agreed tooling; your own estate's configuration determines what applies.
MREF and your next platform decision
Planning your move from TRIRIGA to MREF?
IBM's successor to TRIRIGA is Maximo Real Estate and Facilities (MREF), within Maximo Application Suite. Compare a support bridge, the MREF route, and staged replacement. Understand the dependencies and evidence gaps before committing to a destination. FORGE works with both platforms, so the evidence you gather on TRIRIGA can be checked again on MREF after the move.
A date for your plan
30 September 2027
Base support changes for TRIRIGA/TAS Application 11.6 and Platform 5.0. Paid support options have different scope and terms.
Read IBM's transition termsBuilt around your next question
Expert context.
Across the whole team.
Test and assurance teams
“What should we verify if this changes?”
Follow related workflows, forms, reports, integrations, and business objects to build a traceable regression scope from live estate evidence.
Developers and consultants
“What does my change touch?”
Trace dependencies in an unfamiliar estate. Find the context for your next change without asking a specialist to repeat every lookup.
SMEs and architects
“Is the answer complete enough to act on?”
Review sources, missing evidence, and cross-object dependencies. Focus your experience on the decisions that need it.
Delivery leads
“Can we estimate and hand over with confidence?”
Reduce time spent finding context, expose hidden scope earlier, and keep the investigation evidence attached to estimates, approvals, and handover.
Evidence you can question
An answer should show its working.
A dependency count is useful only when you know what it covers. FORGE can return sources, scope, warnings, and completeness limits, so missing evidence becomes the next investigation step.
Tool policy comes first
The enabled tool list and the TRIRIGA integration identity define the reachable scope. Operators choose the exact tools for each environment, and every change to that choice is versioned and audited. AI output does not grant permission.
Writes are an explicit decision
Read and change capabilities are separated. Authoring, deployment, and log tools stay off until enabled for the named environment, and an Object Migration deploy waits for a person to approve the plan.
Evidence carries context
Results can include source identity, confidence, warnings, related objects, and completeness boundaries instead of an unexplained total.
Deployment boundaries stay visible
Each delivery model states where the AI, tooling, credentials, logs, bridge, and TRIRIGA environment are operated.
A practical place to start
Your estate.
Your AI. Clear boundaries.
Start with Bring your AI: your approved AI client, AJAEX-operated tooling, and a signed bridge in your TRIRIGA or MREF environment. Selected tool data passes through AJAEX. Agree the access and data flow before connecting.
Enterprise and service operators
Make one or many estates quicker to understand and safer to change while keeping every customer, environment, and operating boundary explicit.
Straight answers
Before we
connect.
What is MREF Tools?
MREF Tools is AJAEX's home for tooling around IBM Maximo Real Estate and Facilities (MREF), the platform formerly known as IBM TRIRIGA. Its first product is FORGE by AJAEX, which equips your approved AI client to support, investigate, design, change, and verify work on a TRIRIGA estate. The MREF Tools site is independent of IBM.
What does FORGE add to an AI assistant?
FORGE supplies TRIRIGA-specific tools that the approved AI client can call against your agreed environment. That gives an investigation access to estate configuration and relationships through a controlled integration. The result still needs source checking and technical judgement, particularly where access or evidence is incomplete.
How is FORGE available today?
FORGE is currently available through a scoped Bring your AI paid pilot, usually in one non-production environment with an approved tool allow-list. Managed is offered as a private preview, while Private is available for design-partner engagements.
Does FORGE only read the estate?
No, although the entry scope can be read-oriented estate intelligence. FORGE also authors workflows, forms, portals, reports, and data-model and Web API definitions through native platform paths, creates and updates records, moves Object Migration packages between your environments after a person approves the plan, deploys custom JARs through a signed path, and reads the result back. These capabilities are enabled only for the agreed model, environment, and policy.
Which AI tools can connect to FORGE?
Claude Code, Codex, and other MCP-capable clients can connect to FORGE when they support the configured MCP transport and authentication. Each person or client can have a named access key with its own tool scope, expiry, and optional daily limit. The tools and data each client can access remain limited by the selected deployment model, environment policy, and customer-approved allow-list.
Does customer data stay inside our environment?
That depends on the delivery model. In hosted models, selected tool arguments, results, and audit metadata traverse AJAEX infrastructure. A managed AI workspace can also involve the selected AI provider. Private is designed for customer-operated boundaries, subject to the agreed AI, licence, update, and support paths.
Can FORGE take on our TRIRIGA support and change workload?
FORGE can help your team take on routine support investigations, technical diagnosis, design preparation, and approved implementation and release work. Agree which responsibilities move into the engagement, which instances are connected, and how escalation and production approval work. Response hours, service levels, infrastructure operations, and specialist coverage are separately agreed.
Is MREF supported?
Yes. FORGE works with MREF, IBM's successor to TRIRIGA within Maximo Application Suite, as well as with IBM TRIRIGA. That gives you one approach on both sides of a migration: inventory the TRIRIGA source, assess dependency and integration risk, plan the move, then read the MREF target back and verify it. The tools enabled for each environment are agreed as usual.