For IBM TRIRIGA and IBM Maximo Real Estate and Facilities
Modern developer tools for IBM TRIRIGA.
Ask in plain English. Get answers from live TRIRIGA data in seconds. REST API, MCP metadata graph, AI-assisted debugging, all running inside your existing TRIRIGA instance. Two JARs, deploys in minutes, fully reversible.
The problem
TRIRIGA is a powerful platform. The developer loop is stuck in 2010.
Modern apps ship with REST, observability, and AI hooks out of the box. TRIRIGA shipped before any of that was standard, and it shows.
- No modern REST API
- No programmatic metadata access
- Debugging means clicking through the UI
- Server logs need admin console access
- New developers take 6+ months to be productive
- AI tools cannot see any of it
How it works
TRIRIGA becomes scriptable, queryable, and AI-readable.
A lightweight servlet runs inside your TRIRIGA instance and exposes the platform through a modern REST API and a machine-readable metadata graph. An MCP layer plugs in watsonx Code Assistant, Claude, or any MCP client. Out of the box, LLMs do not know TRIRIGA. Forge is the layer that gives them live, queryable context.
Setup takes minutes. Deploy the servlet, connect the AI, start asking questions.
User jsmith cannot click Approve. Three reasons stack:
- Record is in state In Progress; the Approve transition requires Pending Review.
- jsmith sits in org EMEA-Eng, which lacks Approver on this business object.
- The published override on triApprovalGate hides Approve when triAssignedToCN is null. It is.
Quickest unblock: assign the record. Permanent fix: add jsmith to EMEA-Approvers, or relax the override.
Representative MCP session. Forge plugs into Claude Desktop, Codex, VS Code, watsonx Code Assistant, or any custom MCP client. Tool names and outputs are illustrative.
What teams can do
Replace hours of investigating with minutes of asking.
Not just developers. Analysts mapping how a process flows. Project managers checking status. Auditors asking who can do what. Operations teams chasing a work order. Anyone who needs to get something done in TRIRIGA, or understand how it works.
Instead of
An hour clicking through the UI to debug a hidden button
They ask
“Why can't user jsmith see the Approve button on record 12345?”
~1 minute
Instead of
Hours SSHing into the server and grepping log files
They ask
“Show me today's server errors and what caused them”
~2 minutes
Instead of
An afternoon of trial and error with TRIRIGA's v2 query API
They ask
“Query all active work orders created this month, sorted by priority”
Under a minute
Instead of
Two weeks of TDD archaeology to figure out how a process works
They ask
“How does the work-task lifecycle actually flow on this instance?”
~2 minutes
Instead of
Email chains with security to map who can approve what
They ask
“Who can approve a triProject for the London region right now?”
Under a minute
Actual response time depends on your TRIRIGA instance, network, and the volume of data the query has to retrieve.
Under the hood
Everything the servlet does, in one place.
OData-style queries
$top, $filter, $orderby. Clean JSON, no v2 API workarounds.
Record diagnostics
State, security, GUI, workflow, in one call. Explains why an action is or isn't available.
Metadata discovery
Modules, business objects, fields, forms, workflows. Live and queryable.
Workflow dry-run
Run workflows against real records. No side effects.
Session management
Find and clean up leaked sessions before they crash servers.
Document operations
Create, download, upload, replace. One API call.
MCP metadata graph
Purpose-built for AI navigation. Works today with watsonx Code Assistant, Claude Desktop, VS Code.
Release automation
Object Migration Manager packages from your release pipeline. Promote TRIRIGA config like code.
Legacy IBM TRIRIGA instances
Map a legacy TRIRIGA without paying to rediscover it.
Plenty of organisations run a TRIRIGA instance nobody internally fully understands. The original team has moved on, the TDDs are years stale, and the only people who can answer “what does this workflow do, and what depends on it?” are specialist support firms charging specialist day rates to find out. Forge inverts that. The metadata graph enumerates every workflow, business object, field, form, and association live from the running system, so an internal developer can answer the questions a specialist would have charged you for.
Live business-process mapping
Forge walks the live system and surfaces what each workflow actually does, what fields it touches, what triggers it. No more relying on a TDD nobody updated since 2019.
Cut the specialist-support spend
Specialist TRIRIGA support contracts often sit in the six-figure annual range per instance. With Forge in place, your internal team handles day-to-day investigation and you reserve the specialists for genuinely deep work.
Stay productive on legacy
If you are not ready to migrate to MREF, Forge keeps your existing TRIRIGA team productive on the platform you already paid for, with modern tooling that feels like 2026.
MAS / MREF migration
September 2027 is closer than it looks.
IBM TRIRIGA support concludes 30 September 2027. New TRIRIGA SaaS orders ended 28 January 2026. The path forward is IBM Maximo Real Estate and Facilities (MREF) on Maximo Application Suite. Every TRIRIGA practice and internal team in the world now has the same year on the calendar.
Forge makes the squeeze workable. Ship faster on your existing TRIRIGA right now, then use the same metadata graph to validate parity as workflows move to MREF. Same servlet shape on TRIRIGA Platform, TAS 11.x, and MAS 9.1+ (validating).
Who it's for
Built for the teams who actually deliver TRIRIGA.
TRIRIGA practices
Same headcount. More output.
If your team delivers TRIRIGA work for clients, you're competing on senior SME availability. Forge turns one-to-two-day investigations into minutes, on every developer in your practice. No salary war.
For practicesIBM Services and Business Partners
Built for the teams who actually deliver TRIRIGA.
Compatible with watsonx Code Assistant via MCP, deploys cleanly into IBM environments, and uses TRIRIGA's own auth and security model. A force multiplier for IBM Services and IBM Business Partners.
For IBM partnersEnterprise TRIRIGA teams
Your internal team gets a senior SME at every desk.
Estates, FM operations, and engineering teams running TRIRIGA in-house. Onboard new developers in days instead of months. Cut the queue of one-line questions sitting on senior architects.
For enterprise teamsWhy teams trust it
Lightweight, native, reversible.
Zero infrastructure
Deploys inside your existing TRIRIGA. No additional servers, no middleware, no database changes.
Your security model
Uses TRIRIGA's native authentication and org / geo filtering. No bypass, no parallel auth.
Fully reversible
Remove the JAR files, restart TRIRIGA, it's gone. No traces, no migrations to unwind.
Regional data residency
AI inference runs in the AWS region of your choice, or via your own AI client. Data stays where it should.
- Running against live TRIRIGA environments today
- Two JAR files. No changes to TRIRIGA itself
- Setup takes minutes, not weeks
- Uses TRIRIGA's own org and geo security model
- Bring your own AI client (watsonx Code Assistant, Claude Desktop, VS Code, custom)
See it on your TRIRIGA.
No preparation needed from your side. A non-production URL and credentials, and we can have AI answering your developers' real questions on a real record within hours.