All learning series · Connector · Part 1
Connector for TRIRIGA
Define the handoff between facilities requests and maintenance execution.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Connector for TRIRIGA? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Connector for TRIRIGA?
The TRIRIGA integration moves facilities records between Maximo and TRIRIGA. The 9.2 install table does not list a Maximo Connector for TRIRIGA AppPoint quantity. TRIRIGA is licensed on its own, and a specific App Connect pattern between the two suites is listed as non-charged.
Before configuration
Confirm the integration package in your catalog, the TRIRIGA entitlement, and which record types the package supports. Do not price it as the SAP connector’s 80 points unless your agreement says so.
Before the first successful journey
One building or location mapped on both sides, and one request that becomes work in the owning system.
Before production use
Both suites have owners. A successful mapping file is not a request that created work.
Licensing, entitlement and AppPoints
The MAS 9.2 install table does not list a Maximo Connector for TRIRIGA quantity. Do not copy the 80-point SAP, Oracle or Workday install figure onto it. The same guidance says use of IBM App Connect Enterprise is non-charged when one end of the pattern is Maximo Application Suite and the other end is IBM TRIRIGA Application Suite, IBM Environmental Intelligence Suite, IBM TRIRIGA Portfolio Data Manager, IBM TRIRIGA Application Platform, or IBM Facilities and Real Estate Management on Cloud. That non-charged pattern is not a licence for TRIRIGA itself. TRIRIGA users and Maximo users follow their own entitlements. Anyone who creates or updates a Maximo-owned record still needs a Maximo user entitlement.
Keep four facts separate for the TRIRIGA integration. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Confirm the integration component’s name and version on the Manage workspace, and confirm TRIRIGA opens for an administrator of that suite. Installed means both sides are present. Configured means a location mapping and an endpoint exist. Usable means one request in the source becomes one work record in the target.
Foundation configuration
You need a building or location in both systems with a shared identifier, the organization, and the request type the package supports. Space and people records are TRIRIGA’s or Maximo’s depending on the flow you picked. Do not assume a real-estate lease module is part of this connector.
Product configuration
Enable the package’s flow in one direction first. Map the location key. Grant the integration identity the object structures on the Maximo side and the equivalent access in TRIRIGA. Review a default that creates Maximo work from every TRIRIGA request before you have agreed the work type.
Infrastructure and integration
Both suites need a route, TLS and an identity. App Connect, if that is the pattern you use, has the VPC limits the licensing guidance states for App Connect with Maximo. Capacity follows those limits and the TRIRIGA environment, not a guessed transaction rate.
Data and operational readiness
The first journey is one fictional building, one request, and one work record read back with that building’s key. A second send stays on the same work record. A missing building is data. A refused identity is access. An unmatched request type is the package’s scope.
Setup order for a TRIRIGA flow
- 1. TRIRIGA entitlement and the Maximo integration component No TRIRIGA connector quantity on the 9.2 install table. App Connect between these suites is the non-charged pattern the guidance names.
- 2. One supported direction and record type From the package you deployed.
- 3. A shared building or location key The same identifier on both sides.
- 4. One request read back as work Then a second send that does not duplicate it.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| No assumed install quantity | The 9.2 install table omits this connector. The SAP, Oracle and Workday rows are 80 and do not transfer. | Mandatory | Proof of entitlement. The 9.2 install table. The catalog name of the component you deployed. | The catalog component recorded by its own name, with TRIRIGA licensed on the TRIRIGA agreement. | Read the install table and your agreement side by side. | An 80-point connector line is entered for TRIRIGA. | Remove that quantity unless the agreement prints it for this component. | Licensing in Maximo Application Suite 9.2 |
| The non-charged App Connect pattern, only when that is the integration you run | The guidance allows that pattern between MAS and the listed TRIRIGA products without an extra charge for that use. | Conditional | The App Connect entitlement section of the 9.2 licensing guidance. | One flow with MAS at one end and a listed TRIRIGA product at the other. | Confirm both ends are in the list before you treat the pattern as non-charged. | App Connect is used for a third system and still treated as covered. | License that other pattern separately. | Licensing in Maximo Application Suite 9.2 |
| TRIRIGA entitlement | The pattern does not include TRIRIGA users or TRIRIGA itself. | Mandatory | The TRIRIGA agreement and TRIRIGA’s own administration. | A TRIRIGA administrator can open the building record. | Sign in to TRIRIGA and open the training building. | Maximo is ready and TRIRIGA access is missing. | Complete the TRIRIGA entitlement and the user setup. | Licensing in Maximo Application Suite 9.2 |
| A shared location key | The request has to land on the same building. | Mandatory | Locations or buildings in both systems. | Building B-1 with the same code in Maximo and TRIRIGA. | Query the code on both sides. | The request arrives and creates work with no location. | Map the code before the first request. | Modules and applications in Maximo Application Suite 9.2 |
| One supported request type | The package’s direction and record type are the scope. | Mandatory | The integration flow you enabled. | One service request that the package says it accepts. | Read the package description and match the request you send. | An unsupported request is used as the test. | Send a type the package lists. | Modules and applications in Maximo Application Suite 9.2 |
| One work record read back, and no duplicate on the second send | Delivery is the test. | Mandatory | The target work application, queried by the request key. | One work order or the target record type, key B-1-REQ. | Query it after the first send and again after the second. | The target has nothing, or it has two records. | Fix the flow and the key before production. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- The catalog component and the TRIRIGA agreement are identified, with no borrowed 80-point install.
- You know whether App Connect is the pattern and whether both ends are in the non-charged list.
- Both applications open for their administrators.
- A building code is chosen.
B. Ready for the first end-to-end journey
- The building exists on both sides with the same code.
- One supported request is sent.
- The target record is readable by that code.
- A second send does not create a second record.
- The integration identity cannot administer either suite.
C. Ready for production operation
- Each suite has an owner.
- Maximo user entitlement follows the ownership of any record people update.
- The schedule fits both maintenance windows.
- A failed send is split into data, access and the path between the suites.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- A supported connector package and training environments.
- A documented source request and corresponding target work process.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
IBM publishes predefined integrations between the Maximo and TRIRIGA suites. Select the supplied flow that matches your required business exchange before designing extensions.
A facility/location and a maintenance asset can have different identifiers and ownership. A shared building description does not establish a reliable mapping.
Topics in this series
- Business handoff
- Location identity
- Supplied flow setup
- Status correspondence
- Replay and reconciliation
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Review the supplied integration flow and record supported directions and record types.
- Map one fictional building/location and any required organizational identifiers.
- Configure the flow using the package instructions and training endpoints.
- Send one request or update supported by that flow and inspect its target record.
- Trace the supported response/status exchange and test a duplicate delivery.
03 · Practical example
Fictional teaching example
A fictional facilities help desk requests a cooling-system repair. The exercise preserves the originating request ID when work is created so a later status message updates the right request.
04 · Practice and verify
Create a handoff sheet with source key, target key, mapping, owning system and return status.
Expected result
The same business request is traceable across both systems; retries do not create unintended duplicate work.
Common mistakes
- Assuming every desired object has a predefined flow.
- Synchronizing status codes without agreeing their business meaning.
05 · Advanced concepts
Extend to cancellation, reassignment and failed return messages. Keep property/space ownership and maintenance ownership explicit.
IBM references
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench