Assetize

All learning series · Suite application · Part 1

Maximo Mobile

Prove the offline-to-server work cycle, including errors.

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 Mobile? 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 Mobile?

Maximo Mobile is how a technician works the records Manage already has. The 9.2 guidance includes it at Limited, Base and Premium. A third-party mobile client still needs a user tier.

Before configuration

The mobile service is available, the technician has a tier, and the device can reach the workspace.

Before the first successful journey

One assigned work order, the asset and the location on the device, online first.

Before production use

Offline scope, push credentials and lost-device handling have owners. A login screen is not a completed work order.

Licensing, entitlement and AppPoints

The MAS 9.2 application table includes Maximo Mobile at Limited, Base and Premium. Limited use is three modules, and the table’s Mobile row also names Maximo Collaborate or third-party mobile. A third-party mobile client that updates Maximo-owned records needs the same kind of user entitlement as a Maximo user. There is no Mobile install quantity on the install table. Apple and Google developer accounts, push credentials and device management are third-party. Collaborate’s call path is the Collaborate course.

Keep four facts separate for Maximo Mobile. 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 mobile application is deployed for this Manage version and that a technician can sign in. Installed means the app connects. Configured means the technician’s group and site are right. Usable means the assigned work order opens on the device and a saved update is visible in Manage.

Foundation configuration

The work order, the asset, the location and the labor record have to exist in Manage before the device can show them. Crafts and assignments decide whose work downloads. Attachments and specifications follow the work. They are not a reason to skip the first online save.

Product configuration

Assign the work to the technician. Grant the mobile applications and the work-order actions they need. Set the offline package only after the online save works. Review the default download so the device does not pull every site.

Infrastructure and integration

The device needs a route to the workspace URL, with TLS that the device trusts. Push, if you use it, needs the vendor credentials. Offline use needs storage on the device and a sync window. No GIS or TURN server is required to complete a work order.

Data and operational readiness

The first journey is one work order assigned to the technician, opened on the device, updated, and read back in Manage. A second user sees that update. A missing assignment is data. A refused login is the tier or the group. A save that never reaches Manage is the path or the sync.

Setup order for a technician

  1. 1. User tier Limited within three modules, or Base or Premium. No install line.
  2. 2. Work, asset, location, labor In Manage, before the device.
  3. 3. Assignment and security group The technician’s own user.
  4. 4. Online save, then offline Read the update back in Manage.
Readiness for Maximo Mobile
RequirementWhy neededMandatory/Conditional/OptionalWhere to configure or verifyMinimum working exampleVerification procedureConsequence if missingRemediationSource
A Mobile user tierLimited, Base and Premium include Mobile. Limited is three modules. Third-party mobile that updates Maximo-owned work needs a user entitlement too.MandatorySuite administration → Suite → Administration → AppPoints Usage. Manage → Security → Security Groups, and the suite user type.Technician TECH-M on Limited, with the work applications inside the three modules.Sign in on the device and read the tier on the dashboard.A shared device login is used for every technician.Give each person a user and a tier.Licensing in Maximo Application Suite 9.2
The mobile app for this Manage versionThe client and the workspace have to match.MandatorySuite administration → Catalog and the store or enterprise build you install.The supported client connects to this workspace.Sign in and see the workspace name you expect.The client opens a different environment.Point the client at this workspace.Modules and applications in Maximo Application Suite 9.2
An assigned work order with its asset and locationThe device shows work. It does not invent the asset.MandatoryWork Order Tracking, labor assignment, the asset and the location.WO-M assigned to TECH-M, asset and location filled.Query the assignment, then find WO-M on the device.The device syncs and the list is empty.Assign the work to that labor record.Modules and applications in Maximo Application Suite 9.2
A route the device can useTLS and DNS from the device network.MandatoryThe workspace URL, certificate and any proxy.The device opens the workspace URL and signs in.Complete a sign-in on the technician’s network.The office network works and the yard does not.Open the yard path.Modules and applications in Maximo Application Suite 9.2
An online update read back in ManageThe save has to land on the work order.MandatoryThe mobile work order and Work Order Tracking.A status or a comment saved on the device.Refresh the work order in Manage and see the same change.The device says saved and Manage is unchanged.Repeat online. Treat a local-only save as sync still outstanding.Modules and applications in Maximo Application Suite 9.2
Offline scopeOffline is a second step with a bounded set of records.OptionalThe mobile offline configuration.Leave offline off until the online save works. Then one work order available offline.Change the work order offline, reconnect, and read it back.The first test is offline and the failure is ambiguous.Finish the online path first.Modules and applications in Maximo Application Suite 9.2

A. Ready to configure

  • The technician has a tier that includes Mobile.
  • The client is installed and pointed at this workspace.
  • One work order is assigned to that person.
  • The device network can open the workspace URL.

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

  • The technician signs in and sees the assigned work order.
  • An online update is visible in Manage.
  • A user without the assignment does not see that work order on their device.
  • Offline, if you enable it, syncs the same way.

C. Ready for production operation

  • Each technician has their own user. Lost devices have a disable path.
  • Push credentials, if used, are production credentials.
  • The download scope is the site and the assignment, not every work order.
  • Support can tell a refused login from a missing assignment and from a failed sync.

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.

Before you start

MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.

  • Supported Mobile client connected to a training Manage environment.
  • A technician test account and a small assigned work population.

IBM sources + Assetize exercise

01 · Basics — Understand the building blocks

Maximo Mobile supports online and offline work and synchronization. Data visible on a device and data accepted by the server can be at different stages.

Before an offline task, confirm that the necessary records and reference data have been downloaded.

Topics in this series

  • Users and data scope
  • Initial synchronization
  • Offline execution
  • Error correction
  • Conflict and reconnect testing

02 · Configuration — Work through the setup

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

  1. Sign in online and synchronize the selected training records.
  2. Open the intended work order and confirm required reference data is present.
  3. Disconnect and record a supported work update or actual transaction.
  4. Reconnect, synchronize and inspect any pending or failed changes.
  5. Reread the server record in Manage and compare values with the device.

03 · Practical example

Fictional teaching example

A fictional technician records one labor hour offline. Seeing it on the device is the first observation; seeing the accepted transaction on the correct Manage work order completes the test.

04 · Practice and verify

Run one successful synchronization and one controlled validation-error case. Record both device and server states.

Expected result

Accepted changes appear once on the correct server record; a rejected update remains visible for correction.

Common mistakes

  • Treating a local save as server acceptance.
  • Testing only with uninterrupted connectivity.

05 · Advanced concepts

Explore record selection, conflicts, attachments and offline maps where supported. Test reconnecting after server-side changes.

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