Assetize

All learning series · Connector · Part 1

Connector for TRIRIGA

Define the handoff between facilities requests and maintenance execution.

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 · Not lab-verified

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.

  1. Review the supplied integration flow and record supported directions and record types.
  2. Map one fictional building/location and any required organizational identifiers.
  3. Configure the flow using the package instructions and training endpoints.
  4. Send one request or update supported by that flow and inspect its target record.
  5. 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 guidance, not claims of executed lab procedures. Reviewed 2026-10-01.

Maximo ecosystem overview · Manage learning paths · Practice data in Workbench