Tried and tested on TRIRIGA and MREF.
Tools your own AI client uses to manage, maintain and fix TRIRIGA and MREF.
Follow 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.
Tools across metadata, records, runtime and confirmed change. Tool names shown without their tririga_ prefix.
Ways to run it
- Use our AI modelAvailable now, recommended
- Bring your own AIAvailable now
- Local estate licencePriced on your estate
Illustrative relationship map. Not a live customer result.
Your own AI client
Non-production first
A person confirms every change
A worked example
Ask, look up, propose, confirm.
A routine change can mean hours moving between Data Modeler, Workflow Builder, forms, and queries, then waiting for the person who knows the history. With the tools, your AI client looks it up in the agreed environment, proposes the change, and waits for a person to confirm it.
Email the requester when a request is submitted
Worked out in 2m 14s · Demo data01 · Ask
“I would like to email the requester of a service request when it is raised and submitted.”
02 · Look up
The tools checked the instance and found that TRIRIGA already ships this: the Submit action runs a workflow that notifies the Requested For person.
03 · Propose
Verify the existing setup and switch it on, then customise it if needed. No new workflow to build.
04 · Confirm
Any change the AI client proposes waits for a person to confirm it before it is written.
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.
The tools help 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 everyday configuration questions, put to the tools on a demo TRIRIGA with made-up data. The tools read the instance's own metadata. Timings are as measured at the time.
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.
What was asked
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 Platform 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.
How it is kept safe
Plain facts, before you connect anything.
Your IT team will ask where data goes, who holds the password and who can change what. Here are the short answers. The security pack has the long ones, including what is still open.
Your own AI client
Your AI client and model, under your contract. We run no model in this way of buying, and we do not train models.
Non-production first
The guided start runs in one non-production environment. Production stays read-only unless you agree otherwise in writing.
Credentials kept apart
The TRIRIGA service user's password is held in a per-customer secret store, not in your AI client.
Tool policy
You choose the tools for each environment. Write tools stay off until the policy for that environment turns them on.
A person confirms every change
Your AI client proposes; a person confirms each change before it is written to TRIRIGA.
Audit log
Every tool call is logged with environment, action and outcome, without secrets, and kept for 90 days.
A clear way out
Remove the bridge and the service user, and the tools can no longer reach your instance.
What your AI client can do with the tools
Manage, maintain and fix.
Config questions answered in minutes from the instance's own metadata, log scans, outbound integrations, and business objects or forms built in non-production. Each change confirmed by a person and logged.
Day-to-day support and incident investigation
Server-side Java investigations
Change proposals, FDDs, and TDDs
Implementation alongside your team
Packaging, deployment, and verification
Prices
Start with four weeks. Then pay for the defects you agree each quarter.
Priced on the senior TRIRIGA hours each defect saves you, measured on your own tickets.
1. Start
£3,950 fixed
Plus VAT
Guided start for small teams: set-up and four weeks in one agreed non-production environment.
- Tools connected to your AI client, writes on in non-production only
- Kick-off, a weekly 30-minute check-in and an agreed task list
- A close note at week four: what was asked, answered and built, time saved, findings and a recommendation
- Does not start a subscription
- Larger teams: measured two-month run, £5,950 a month for two months, up to 30 real defects a month, read-only; the final month is credited against your first subscription month
2. Use our AI model
Ask us
Plus VAT
Our workspace, AI model, tools and gateway, working on your own TRIRIGA instances. Our recommended way to run the tools.
- Priced on the number of defects a month you agree with us, set from your own tickets and reviewed each quarter
- Includes our workspace, our AI model and a usage allowance
- Writes only in agreed environments, each confirmed by a person
- 12-month minimum, billed monthly in advance, then 30 days' notice
- Up to 20 environments included; larger estates carry an estate charge
- Prefer to pay for inference on your own model account? Bring your own AI: we connect the workspace to the provider you choose (Anthropic, OpenAI or AWS Bedrock), under your contract, on the same terms
Also available
Cover add-on
£950 a month
Cheapest way in if you already have AJAEX TRIRIGA cover. Add the tools to Essentials or Standard cover: up to 15 defects a month and 3 environments, running with your cover agreement and ending with it. Included in Advanced cover (15 defects) and Enterprise cover (40). Cover itself is sold by AJAEX LTD; the tiers and prices are on our support page.
Ask us about Results as a Service: a price for each fix your engineer accepts, with the acceptance terms set out in your order. 12-month minimum, billed monthly in advance, then 30 days' notice.
Add-ons for TRIRIGA
- MFA for TRIRIGAEarly access
Ask us
A second sign-in step for TRIRIGA users: a code from an authenticator app as well as the password. Priced per production environment. Without cover: 12-month minimum, billed monthly in advance, then 30 days' notice; with cover it runs with your cover agreement.
- SharePoint connectorEarly access
Ask us
Publishes TRIRIGA Document Manager folders and files to SharePoint. Priced per production environment.
- ServiceNow connectorEarly access
Ask us
Lets ServiceNow raise and read TRIRIGA service requests. Priced per production environment.
Partner programme
Partner pricing available, ask us.
All prices plus VAT.
MREF and the 2027 date
Planning your move from TRIRIGA to MREF?
IBM's successor to TRIRIGA is Maximo Real Estate and Facilities (MREF), within Maximo Application Suite. Someone has to list every business object, workflow, form and integration that will move. The tools build that list from your TRIRIGA instance.
A date for your plan
30 September 2027
IBM base support for Platform 4.5 and Application 11.5 ended on 30 September 2026. Only Platform 5.0 / Application 11.6 still has base support, and that changes on 30 September 2027.
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.
Enterprise and service teams
Make one or many TRIRIGA estates quicker to understand and safer to change, with every environment and boundary explicit.
Straight answers
Before we
connect.
What are TRIRIGA and MREF tools?
Tools your own AI client uses to manage, maintain and fix TRIRIGA and MREF, with a person confirming every change before it is written. Your AI client calls the tools against an agreed environment, so answers come from the instance's own metadata rather than from memory. AJAEX LTD sells and supports them.
Which AI clients can connect?
MCP-capable clients such as Claude, Copilot and Cursor can connect when they support the configured transport and sign-in. The tools each client can reach stay limited by the environment's tool policy and the TRIRIGA service user's permissions.
Do the tools only read the estate?
No, although the start can be read-only. Where the policy for a named environment allows it, the tools can author workflows, forms, reports and data-model definitions through TRIRIGA's own paths, and create and update records. A person confirms each change before it is written.
Where does our data go?
With Bring your own AI, prompts stay with your AI client and model provider, under your contract. Tool names, arguments and results pass through our gateway in AWS London (eu-west-2). Whether the full prompt does depends on your client. We do not train models on your data.
Can we start without touching production?
Yes. The guided start is non-production only, and production is read-only unless agreed in writing.
Does it work with MREF?
Yes. Tried and tested on TRIRIGA and MREF, with the same person-confirmed changes on both.
What certifications do you hold?
AJAEX LTD holds Cyber Essentials Plus (renewal 13 November 2026). Cyber Assurance and ISO 27001 certification are in progress. It holds no ISO 27001 or SOC 2 certificate today, and no independent penetration test has been run. Ask for our security pack: it sets out the controls, the open items and how each is being closed.