Support and delivery across your TRIRIGA estate
Run, support, and evolve TRIRIGA.
FORGE equips your AI with the tools to investigate support issues, diagnose server-side Java, prepare proposals and designs, and implement approved changes across multiple TRIRIGA instances.
Setup, pilot, and subscription pricing are agreed for your scope. Contact AJAEX for a proposal.
See pilot and subscription scopeFollow the dependencies
What depends on this field?
Trace the references. Build the test scope.
Follow the connections. Review the evidence before deciding what to change.
Illustrative relationship map. Not a live customer result.
Live estate context
Traceable dependency evidence
Your team stays in control
Your AI, equipped for TRIRIGA
An ongoing support and delivery partner.
Take on the work of running TRIRIGA from end to end: investigate incidents, understand server behaviour, propose changes, prepare designs, implement approved work, and verify the release across connected instances.
Day-to-day support and incident investigation
Take on routine support work with live record, security, workflow, integration, and runtime evidence.
Explore this capabilityServer-side Java investigations
Connect server exceptions and JVM behaviour to the application, deployed JARs, and available source code.
Explore this capabilityChange proposals, FDDs, and TDDs
Turn business requirements and live estate evidence into reviewable proposals and design documents.
Explore this capabilityImplementation alongside your team
Move from an approved design into native TRIRIGA configuration and controlled application changes.
Explore this capabilityPackaging, deployment, and verification
Carry approved work through Object Migration, controlled JAR releases, and checks on the target environment.
Explore this capabilityOperations across multiple instances
Use one support and delivery approach across authorised development, test, UAT, and production instances.
Explore this capabilityStart 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.
Watch the overview
23 seconds · No sound neededRead the video transcript
One field. A wider impact. What depends on the thing you are about to change?
Follow the connections: workflows, forms, queries, and integrations. Build a test scope.
See the evidence. Know its limits. Where did it come from? What was checked? What still needs review?
Understand the impact before you change TRIRIGA. Bring your TRIRIGA question to tririgatools.com.
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.
Bring a question to a demonstration- 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.
MREF and your next platform decision
Planning your next move from TRIRIGA?
Compare a support bridge, IBM's MREF route, and staged replacement. Understand the dependencies and evidence gaps before committing to a destination.
Compare MREF and your optionsA 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 termsProduct pipeline
Maximo Tools
IN PROGRESSTools for IBM Maximo are in active development. Scope and availability will be shared as development progresses.
Discuss Maximo ToolsBuilt 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.
Review deployment and securityTool policy comes first
The enabled tool list and the TRIRIGA integration identity define the reachable scope. AI output does not grant permission.
Writes are an explicit decision
Read and change capabilities are separated. Production enablement and any change approval are agreed for the named environment.
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 Customer AI: your approved AI client, AJAEX-operated tooling, and a signed bridge in your TRIRIGA environment. Selected tool data passes through AJAEX. Agree the access and data flow before connecting.
Bring your AI
Customer AI / AJAEX Tooling
Organisations that already have an approved AI client or model account.
Explore a paid pilotManaged workspace
AJAEX Managed
Teams that want one managed workspace and a single service boundary.
Explore this modelPrivate edition
Customer Private
Regulated, sovereign, isolated, or customer-operated environments.
Explore this modelOne question. Four weeks. Evidence to decide.
Start with setup and a four-week Customer AI pilot. Agree the outcome, environment, and commercial terms before access.
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.
For enterprise teamsDelivery practices and global teams
Onboard consultants and testers faster, preserve context across handovers, and keep specialist review focused on the decisions that need it.
For delivery practicesMREF and migration options
Compare a support bridge, MREF, and staged replacement using the same cost, capability, and continuity evidence.
Explore MREF and your optionsStraight answers
Before we
connect.
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 Customer AI / AJAEX Tooling paid pilot, usually in one non-production environment with an approved tool allow-list. AJAEX Managed is offered as a private preview, while Customer Private is available for design-partner engagements.
Does FORGE only read TRIRIGA?
The entry scope can be read-oriented estate intelligence. The wider product also includes guarded authoring, Object Migration, deployment, and verification capabilities, but these 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. 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. Customer 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?
MREF compatibility validation is in progress, so broad support is not yet claimed. Current migration engagements focus on estate inventory, dependency and integration risk, readiness planning, and post-upgrade verification.
Bring the question that keeps coming back.
A field nobody wants to touch. An undocumented workflow. An upgrade with an unclear test scope. Let’s start there.