Assetize

All learning series · Suite application · Part 1

Maximo Collaborate

Remote expert sessions that end as work-order knowledge, and how Collaborate differs from the Maximo Assistant.

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.

  1. Are you ready to use Maximo Collaborate? Licensing and AppPoints, the records that must exist, and three checklists.
  2. Basics
  3. Configuration
  4. Practical example
  5. Practice and verify
  6. Advanced concepts

Are you ready to use Maximo Collaborate?

A technician can call an expert only after the add-on is deployed, two people exist, push can reach the expert, and a STUN and a TURN server are configured. Creating a session record is the record of the request. The live call also needs signalling and a media path.

Before configuration

Know which tier your dashboard assigns when a person is granted Collaborate, and have a cluster that can host the add-on. IBM’s Collaborate 9.2 install topic is the procedure for the deployment.

Before the first successful journey

Two different people, an expert person group, one STUN server, one TURN server, push for the expert’s device, and a work order the technician can open.

Before production use

The TURN server is one you operate or subscribe to, certificates and push credentials are production credentials, and someone owns the path when a call connects and the other person hears nothing.

Licensing, entitlement and AppPoints

Two current IBM topics describe the Collaborate tier, and they do not use the same word. The MAS 9.2 licensing guidance says Collaborate is authorized and concurrent and that AppPoints are based on the Limited tier. The same guidance’s application table says Maximo Mobile includes Maximo Mobile, Maximo Collaborate or third-party mobile at Limited, Base and Premium. The user-access topic for MAS 9.1 and later says the Base entitlement adds Maximo Collaborate and Maximo Health on top of Limited. Grant the Collaborate security group, then read the tier the AppPoints Usage dashboard actually assigns to that person, and apply the Limited ratio or the Base ratio that matches the dashboard. There is no Collaborate line on the install-AppPoints table. A third-party TURN service, Apple and Google push credentials, and any device management suite are licensed by those providers.

Keep four facts separate for Maximo Collaborate. 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

In MAS 9.2, Collaborate deploys from the catalog onto the Manage workspace. Confirm the catalog shows it deployed and the component version, then confirm the Collaborate and Collab Session applications open. Deployed is not the same as a working call. The configuration guide records the screens for the install check, the expert group, the ICE servers and push.

Foundation configuration

You need two people in the site: a technician and an expert. The expert belongs to a person group with Is expert group set. Skills on the expert’s labor record drive the skill match. A work order gives the session somewhere to live. Crafts, calendars and asset hierarchies are useful context and are not what makes the call connect.

Product configuration

Follow the configuration guide for the exact screens. The mandatory path is the add-on deployed, security groups for technician and expert, the expert person group, one STUN and one TURN entry in Collaborate app settings, and push configured so the expert’s device can be invited. Session history in Collab Session is the audit trail. Review the default ICE list before production so a laboratory TURN server is not the one every site uses.

Infrastructure and integration

Signalling is the Collaborate service on the workspace. Media between the two devices uses the STUN and TURN servers you enter. Push uses the MAS push configuration and the vendor credentials for the device platform. The devices need a route to those servers, with DNS and TLS that match the URLs you configured. A single-node topology is called out in IBM’s Collaborate install topic. Read that topic for the cluster you have before you start the deployment.

Data and operational readiness

The first journey needs one work order, the technician, the expert, and the expert group. A session row with status open proves the request was saved. A live call proves signalling, push and the media path as well. If the session saves and the expert’s device never rings, check push and the device identity. If the devices join and there is no audio, check TURN. If the application is missing, check the catalog and the security group.

Setup order for a call

  1. 1. Entitlement tier, read from the dashboard Compare the 9.2 licensing guidance and the user-access topic with the tier this user is assigned.
  2. 2. Collaborate deployed on the Manage workspace Catalog deployment and the applications open.
  3. 3. Technician, expert and expert person group Two people. The group is marked as an expert group.
  4. 4. STUN, TURN and push ICE servers in Collaborate app settings. Push for the invitation.
  5. 5. A work order and a session The session record, then a call between the two devices.
Readiness for Maximo Collaborate
RequirementWhy neededMandatory/Conditional/OptionalWhere to configure or verifyMinimum working exampleVerification procedureConsequence if missingRemediationSource
The tier the dashboard assigns for CollaborateIBM’s 9.2 licensing guidance prices Collaborate at Limited, and the user-access topic adds Collaborate at Base. The dashboard is the assignment that consumes points.MandatorySuite administration → Suite → Administration → AppPoints Usage, after the Collaborate group is granted. Manage → Security → Security Groups, and the suite user type.One technician and one expert, each granted Collaborate, with the tier the dashboard shows written down.Grant the group, open AppPoints Usage, and record Limited or Base for each person. Apply that row’s ratio from the 9.2 guidance.You planned Limited points and the dashboard reserved Base, or the reverse.Match the purchase to the tier the dashboard assigns. Change the groups if they pull in Health, Predict or an industry application and lift the tier.Licensing in Maximo Application Suite 9.2
Collaborate deployed, and the applications openThe add-on runs the signalling service beside Manage.MandatorySuite administration → Catalog → Collaborate, on the Manage workspace. Applications Collaborate and Collab Session.Catalog shows Collaborate deployed. Both applications open for an administrator.Open the catalog tile and both applications. Record the component version beside this check.The configuration screens are absent.Deploy the add-on from the catalog using IBM’s 9.2 install topic for your cluster.Installing and deploying Maximo Collaborate
Two people and an expert person groupThe technician invites a person. The product finds experts from person groups marked as expert groups.MandatoryPeople, Labor, Person Groups. Is expert group on the group.Technician TECH-1, expert EXP-1, group PUMPS with Is expert group selected and EXP-1 as a member.Search for an expert from the technician’s session and see EXP-1 offered from PUMPS.The session screen has nobody to invite.Create the two people and the group before you test push or TURN.User access and entitlements in MAS 9.1 and later
One STUN server and one TURN serverThe devices discover each other through STUN and relay media through TURN when a direct path is blocked.MandatoryCollaborate app settings, ICE servers.One STUN URL and one TURN URL, with the username and credential the TURN server expects.Save the servers, then place a call between two devices on the networks technicians actually use.The session opens and audio or video never starts.Correct the ICE URLs and credentials. A session row can exist while this path is still down.Configuring Collaborate app settings
Push to the expert’s deviceThe invitation travels by push. Online presence uses the same service.MandatorySuite push configuration, and the Mobile device registered to the expert.Push credentials for the platform the expert uses, and EXP-1 signed in on that device.Send an invitation and confirm the device receives it.The session stays open and the expert is never invited.Register the device and the push credentials. Check push before you change TURN.Configuring push notifications
A work order the technician can openThe session is raised from the work and the summary is stored against it.MandatoryWork Order Tracking and Maximo Mobile or the Collaborate application.Work order WO-1 on the training site, assigned so TECH-1 can open it.Open WO-1 as TECH-1 and start Get assistance or Contact expert.The people and the servers are ready and the technician has no work order to start from.Create the work order and grant the technician the work-order application.Modules and applications in Maximo Application Suite 9.2
A TURN subscription or server you operateTURN is a third-party or self-hosted media relay. It is not an AppPoint quantity.ConditionalThe TURN provider’s subscription, or the server you run, plus the firewall path from both devices.A TURN endpoint you control, with capacity for the number of simultaneous calls you expect.Place a call from a network that cannot go device-to-device and confirm media still flows.Calls work on the lab network and fail on the plant network.Allow the TURN ports and host, or subscribe a TURN service that both networks can reach.Interactive Connectivity Establishment (ICE) server

A. Ready to configure

  • You have read the tier on AppPoints Usage for a user who has the Collaborate group, and the proof of entitlement covers that tier.
  • The catalog shows Collaborate deployed and the applications open.
  • The cluster matches the install topic you are following.
  • You have URLs for a STUN server and a TURN server, and push credentials for the device platform.

B. Ready for the first end-to-end journey

  • TECH-1 and EXP-1 exist, and EXP-1 is in an expert person group.
  • WO-1 opens for the technician.
  • The technician creates a session and the session appears in Collab Session.
  • The expert’s device receives the invitation.
  • Both devices join and audio or video is exchanged. A saved session without media is only the first half of this list.

C. Ready for production operation

  • TURN, push and TLS certificates are the production endpoints, with an owner for each.
  • Expert groups match real skills, and labor skills are maintained by the people who staff those groups.
  • A failed invitation is checked as push, a failed media path as TURN, and a missing application as catalog or security.
  • Session history is readable by a supervisor who was not on the call.
  • Device loss and expert absence have a support path that does not depend on one person’s phone.

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.

Maximo Collaborate on the screen

One remote-expert session, from the technician’s phone to the knowledge the next technician finds, then the Maximo Assistant on the same work order. Watch it play, or step through it.

Sample site: pump P-2041 in plant room B2, work order WO 1048, technician M. Reyes, expert J. Okafor.

  1. The job, on the phone (Maximo Mobile · Work order). Do this: Open WO 1048 on your phone. Task 10 says "close the isolation valve". There are two valves in the line. You see: The work order with its asset, location and task. Get assistance sits in the action bar. Why it matters: Collaborate starts from the work the technician is already on, so the session is tied to the work order from the first tap.
  2. Ask for an expert without a call (Maximo Mobile · Get assistance). Do this: Tap Get assistance. Choose Chat only, type the question, attach the photo of the two valves, send. You see: A request with the session type, the question, the skills it needs and the photo. Why it matters: From 9.2 a technician raises a collaboration request without starting a video or voice call, and picks video, audio or chat. A plant room with no bandwidth still gets help.
  3. The request finds the right expert (Maximo Mobile · Request). Do this: Wait. The request goes to experts whose skills match PUMPS and SEALS. You see: Request CS-00217, WAITING, expert group EXPERTS-MECH, two experts matched. Why it matters: Experts are found by skill and keyword. In 9.2 those live on Labor records and Person Groups in Manage, where the rest of your people data is.
  4. The expert answers in the session (Collaborate · Session CS-00217). Do this: As the expert, accept the request. You see it is chat only before you join. Read the question, look at the photo, answer. You see: The session: request details and the messages. The expert names the valve by position, V-12, and asks for a pressure check. Why it matters: The expert guides the work step by step. Everything said and shared here is kept with the session, and the session belongs to WO 1048 and P-2041.
  5. Every session, under Work Orders (Maximo Manage 9.2 · Collab Session). Do this: End the session. In Manage, open Work Orders, then Collab Session. You see: A list of sessions with their work order, asset, type, technician, expert and status. Search and filter work on it. Why it matters: From 9.2 the Collab Session application in Manage is where sessions are reviewed, with their related work orders, assets and participants.
  6. The summary lands on the work order (Maximo Manage 9.2 · Collab Session · CS-00217). Do this: Open CS-00217. Read the summary. Download the summary PDF. You see: The session record: both participants, start and end, the files and annotations, and a summary that names the asset, the valve position and the corrected instruction. Why it matters: The summary is attached to the work order at the end of the session. A summary that names the asset and the position is the one the next technician finds.
  7. Make it findable (Maximo Manage · Document collections). Do this: Add the CS-00217 summary to the PUMPS-SEALS document collection. You see: The summary sits beside the earlier P-2040 session and the manufacturer’s torque table. Why it matters: Summaries added to a document collection are searchable the next time a technician meets a similar incident. Curate by asset class, so knowledge is found by asset and failure, not by date.
  8. The next technician finds it first (Maximo Mobile · Asset P-2041). Do this: A month later, as a different technician, open P-2041 on your phone and look at Documents. You see: The CS-00217 summary is the first document: isolation valve is V-12. Why it matters: That is the return on the session. One corrected instruction, retained with the asset, and nobody calls the expert for the same valve again.
  9. Now the Maximo Assistant, on the same work order (Maximo Manage · Work Order Tracking · Maximo Assistant). Do this: Open WO 1048 in Manage and open the Maximo Assistant. Ask for the open work orders on P-2041 and the last session summary. You see: An answer built from your records: two open work orders and the CS-00217 summary. Mode: retrieve data. Custom tools: none. Why it matters: The Maximo Assistant retrieves records and asset insights and searches IBM Documentation. It creates or edits data only through a custom tool your administrator built. Collaborate puts a person on the job; the Assistant answers from what Maximo already holds.

Before you start

MAS 9.1 and 9.2. The 9.2 steps use the Collab Session application in Manage and the Get assistance option in Maximo Mobile; on 9.1 the same session is reached from the Collaborate home page. Match the component documentation to your installed release and maintenance build before configuring it.

  • MAS 9.1 or 9.2 with Collaborate deployed. On 9.2, deploy it from the Manage Catalog add-on page on a multi-node cluster; IBM states it cannot be installed on single-node OpenShift.
  • Experts and technicians as MAS Core users, with the expert's skills on their Labor record and an expert Person Group, so a technician's skill and keyword search finds them.
  • The ICE server configured on the Collaborate app settings tile in Mobile Configuration, Maximo Mobile on a supported device, and one training work order.

IBM sources + Assetize exercise

01 · Basics — Understand the building blocks

Maximo Collaborate connects a technician on a job with a remote expert over audio, video, chat or augmented reality. The expert guides the work step by step, and the session record names the work order, the expert, the technician, the files and annotations shared, and a summary that is attached to the work order at the end.

The product has carried three names. IBM rebranded Maximo Assist as Maximo Collaborate in MAS 9.1, and from 9.2 Collaborate is an add-on in Maximo Manage, deployed from the Manage Catalog add-on page. Older documentation, licence entries and support pages still say Assist.

In Manage 9.2 the pieces live where the rest of your work lives: the Collab Session application under Work Orders reviews sessions, related work orders, assets and participants and downloads a session summary PDF; Expert Groups and Technicians moved to Person Groups and Labor; the Collaborate app settings tile in Mobile Configuration holds the ICE server settings; users and roles come from MAS Core, which took over user management in 9.1.

The Maximo Assistant is a different product. It is the AI assistant in MAS 9.1 and later, opened from Manage, Health, the Operational Dashboard, asset dashboards and, in 9.2, Maximo Mobile. It retrieves records and asset insights and searches IBM Documentation; what it can do depends on what your administrator configured, and in 9.2 it can act as an agentic assistant or only retrieve data.

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.

Topics in this series

  • Assist, Collaborate and the Manage add-on
  • Experts, Person Groups and Labor
  • Get assistance and Contact expert in Maximo Mobile
  • Collab Session application and summary PDFs
  • Document collections and knowledge reuse
  • Collaborate versus the Maximo Assistant

02 · Configuration — Work through the setup

Use a training environment and match the actions to the IBM guide for your installed build.

  1. Open the training work order in Maximo Mobile and choose Get assistance, or open the Collaborate app and choose Contact expert. Pick the session type: video, audio or chat only. A technician can raise the request without starting a call.
  2. As the expert, accept the request. The session shows whether it is video, audio or chat before you join. Share only the views needed to diagnose the fictional issue and give the step-by-step instruction.
  3. End the session. Open the Collab Session application under Work Orders in Manage and check the session record: the work order, the asset, both participants, the files and annotations, and the summary.
  4. Download the session summary PDF and add the summary to a document collection, so it is searchable the next time a technician meets the same incident.
  5. Sign in as a second authorised technician and search for the retained summary from the work order and from the asset. Then open the Maximo Assistant on the same work order and ask it a data question, to see where each product stops.

03 · Practical example

Fictional teaching example

A fictional technician cannot tell which of two valves the written instruction means. From the work order she chooses Get assistance, chat only, because the plant room has no signal for video. The expert names the valve by its position tag and corrects the instruction. The session summary lands on the work order, is added to the document collection for that asset class, and the next technician at the same pump finds it before calling anyone.

04 · Practice and verify

Run one training session end to end on 9.2: raise it from the work order, choose the session type, end it, review it in the Collab Session application, download the PDF and add the summary to a document collection. Then review the same session as the supervisor.

Expected result

The session record belongs to the training work order and names the asset and both participants; the summary describes the outcome and the corrected instruction; the PDF downloads; a second authorised technician retrieves the summary from the document collection.

Common mistakes

  • Retaining a conversation without the equipment identity. A summary that names the asset and the position is the one the next technician finds.
  • Confusing Collaborate with the Maximo Assistant. Collaborate puts a remote person on the job; the Assistant answers questions from your records and IBM Documentation, and only creates or edits data if your administrator built a custom tool for it.
  • Reading Maximo Assist documentation as if it were current. Assist is the pre-9.1 name, and the 9.1-and-earlier session pages describe the Collaborate home page, not the Collab Session application in Manage.
  • Looking for Collaborate users, experts and technicians in the old places. From 9.1 users and roles are MAS Core's; from 9.2 experts and technicians are Person Groups and Labor records in Manage.
  • Planning a video-first rollout where the field has no bandwidth. The 9.2 chat-only request and the audio option exist for that job.

05 · Advanced concepts

Decide who curates summaries into document collections and how the collections map to asset classes, so retained knowledge is found by asset and failure rather than by date. Check device and network compatibility and the ICE server before a field rollout. Then look at the Maximo Assistant: which object structures are enabled for it, whether the agentic toggle is on, and what a custom tool would be allowed to do on your records.

IBM references

Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.

Configuration guide: every screen and option · Maximo ecosystem overview · Manage learning paths · Practice data in Workbench