Assetize

Maximo Collaborate, Part 1 · Suite application · Part 2

Set up Maximo Collaborate and the Maximo Assistant

Part 2, the administrator’s path: deploy the add-on, give the experts their skills, connect the media server, open the session application to the right people, make summaries findable, then decide what the Maximo Assistant may do.

Sample site: the same plant as Part 1. Administrator A. Patel, expert J. Okafor, technician M. Reyes (all sample).

Are you ready to use Maximo Collaborate? Licensing, foundation data and the three checklists are on Part 1.

What you set up

  1. Deploy Collaborate from the Manage Catalog (Suite administration · Manage · Catalog). Do this: Open the Manage workspace, then Catalog, then Add-ons. Select Maximo Collaborate and deploy it. You see: Collaborate listed with the other add-ons, selected for deployment, on a three-node cluster. Why it matters: From 9.2 Collaborate is an add-on in Maximo Manage and deploys from the Manage Catalog add-on page. IBM states it cannot be installed on single-node OpenShift, so the cluster field matters.
  2. Users come from MAS Core (Suite administration · Users). Do this: Open the expert’s MAS user. Give them Maximo Manage, Collaborate and Mobile. Do the same for the technician. You see: One user record with the three applications ticked and an active status. Why it matters: Since 9.1 Collaborate no longer manages users and roles locally; all user management is at the MAS Core level. There is one place to add an expert or a technician.
  3. Give the expert the skills technicians search for (Maximo Manage 9.2 · Labor · Crafts and Skills). Do this: Open the expert’s Labor record. On Crafts and Skills, add PUMPS and SEALS with the keywords technicians will type. You see: Two expert-level skills with keywords; the search that Get assistance runs matches on these. Why it matters: In 9.2 the Expert Groups and Technicians applications migrated to Person Groups and Labor. Skills on the Labor record are what a technician’s skill and keyword search finds.
  4. Put the experts in a person group (Maximo Manage 9.2 · Person Groups). Do this: Create EXPERTS-MECH and add the four mechanical experts, J. Okafor first. You see: A person group with four members and a default. Requests for pump work route here. Why it matters: The person group is the 9.2 home of what Expert Groups used to hold. Technicians saw it on their request in Part 1.
  5. Connect the media server (Maximo Manage 9.2 · Mobile Configuration · Collaborate app settings). Do this: Open Mobile Configuration, then the Collaborate app settings tile. Enter the ICE server URL, username and credential. Test the connection. You see: The server details, a credential lifetime, and a successful test. Why it matters: The Collaborate app settings tile in Mobile Configuration holds the Interactive Connectivity Establishment server that video and audio sessions need. Set it, and test it, before a rollout that uses video or audio.
  6. Open the session application to supervisors (Maximo Manage · Security Groups). Do this: Open the MAINTSUP security group. Grant read access to the Collab Session application under Work Orders. You see: Supervisors can open Collab Session, review sessions and download summary PDFs; technicians and experts keep their own access. Why it matters: The Collab Session application sits under Work Orders in Manage 9.2 and is secured like any other Manage application: by security group and application access.
  7. Make a home for retained knowledge (Maximo Manage · Document collections). Do this: Create the PUMPS-SEALS collection, name a curator, and associate the centrifugal pump asset class. You see: A collection with a curator and an asset class, seeded with an earlier session summary and the manufacturer’s torque table. Why it matters: Session summaries added to a document collection are searchable the next time a technician meets a similar incident. A collection per asset class is what makes them found by asset and failure, not by date.
  8. Decide what the Maximo Assistant may do (Suite administration · Maximo Assistant). Do this: Open the Maximo Assistant configuration. Turn on the agentic assistant toggle to set up its AI configuration, keep retrieve data, insights and documentation search on, and set the record limit. You see: Capabilities on, a record limit of 50, and no custom tools: the assistant answers from records and creates or edits nothing. Why it matters: In 9.2 the assistant can act as an agentic assistant or only retrieve data, and the agentic toggle must be on to set up the AI configuration. It creates or edits data only through a custom tool the administrator configures. It is not a general-purpose chat bot.
  9. Choose what the assistant may search (Maximo Manage · Object Structures). Do this: Open MXAPIWODETAIL and enable it for the Maximo Assistant. Check the defaults are still on. You see: Six object structures the assistant may search: four enabled by default, two enabled here. Why it matters: The assistant can search for data in any object structure that is enabled for it. MXAPIASSETMETER, MXAPIINVBAL, MXAPIASSIGNMENT and MXAPISERVITEM are enabled by default; work orders and assets are your call.

Components

Component responsibilities at a glance
ComponentWhat it doesTypical output
Maximo Collaborate (Assist before 9.1)Remote expert sessions over video, audio, chat or AR, tied to a work order.A session record with participants, files, annotations and a summary attached to the work order.
Collab Session application (Manage 9.2)Review, search and filter sessions under Work Orders; see related work orders, assets and participants.Session summary PDFs.
Maximo MobileWhere a technician raises a request: Get assistance on a work order, or Contact expert in the Collaborate app; video, audio or chat only.A collaboration request an expert accepts, with the session type visible before joining.
Person Groups and Labor (Manage 9.2)Replace the Expert Groups and Technicians applications; skills on the Labor record drive the expert search.Expert groups and skills a technician can search by keyword.
Mobile Configuration, Collaborate app settingsHolds the ICE server settings Collaborate needs for media sessions.Working connectivity between technician and expert.
MAS Core usersAll Collaborate user and role management since 9.1.One place to add an expert or a technician.
Document collectionsWhere a curated session summary becomes searchable knowledge.A summary the next technician finds by asset and incident.
Maximo Assistant (MAS 9.1 and later)The AI assistant in Manage, Health, dashboards and 9.2 Mobile: retrieves records and asset insights, searches IBM Documentation, agentic or retrieval-only in 9.2 as the administrator configures.Answers from your records and IBM Documentation; data changes only through an administrator-built custom tool.

IBM references

Reviewed 2026-10-01.

Configuration guide: every screen and option