Assetize

Maximo Mobile desk

Maximo Mobile 9.0, from IBM's own pages and the record.

What the app needs on a device, how the shell and the Graphite apps fit together, what happens offline, how it gets deployed and logged into, and what each release added — each statement with IBM's words and page beside it. The fixes, gotchas and API notes on record are in Explore, filtered to Mobile.

By release

What IBM says about Maximo Mobile 9.0

What Maximo Mobile is

  • Maximo Mobile is IBM's role-based mobile product for technicians and supervisors, with apps for work execution, inspections, inventory and service requests on iOS, Android and Windows.

    “Maximo® Mobile is a role-based mobile solution that enables technicians and supervisors to manage work and assets from any location. It includes apps for work execution, inspections, inventory, and service requests, and supports iOS, Android, and Windows devices.” — IBM Docs — Maximo Mobile overview, read 2026-09-12

  • The Technician, Approvals, Inspections and Service Request apps are the core set; IBM publishes their object structures, queries and security authorisations.

    “This article points to information for the object structures, query information, and related security authorization used in the Technician, Approvals, Inspections, and Service Request applications.” — IBM Support — Maximo Mobile application object structures, query information, and security authorization (3 May 2024), read 2026-09-12

Shell, Graphite apps, online and offline

  • The store app is a shell. IBM updates the shell through the public app stores independently of the Graphite applications that run inside it, and keeps the shell runtime backward compatible.

    “IBM can release updates to the shell through public app stores without affecting the functionality of the Graphite Applications themselves. … IBM ensures backward compatibility of the runtime environment that the shell provides to the Graphite Applications, allowing for seamless updates.” — IBM Support — IBM Maximo Mobile architecture (6 May 2025), read 2026-09-12

  • The Graphite apps themselves live in Maximo Manage, as zip files in the MAFAPPDATA table, and the shell pulls a new version whenever Manage has one.

    “The Graphite Applications, developed using MAF, are stored as zip files in the MAFAPPDATA database table, within a BLOB column. … It then updates the files into the shell whenever a new version of the Graphite Application is available in Maximo.” — IBM Support — IBM Maximo Mobile architecture (6 May 2025), read 2026-09-12

  • Data on the device sits in a local JSON store encrypted with a key held in the device keystore; data fetched online is saved there automatically and offline work syncs back when connectivity returns.

    “… a local JSON data store is created on the device … encrypted by using a unique key that is saved in the device's keystore. … data that is retrieved from Maximo Manage is automatically saved to the local data store … when connectivity is restored, local data is automatically synchronized.” — IBM Docs — Maximo Mobile authentication and data flow, read 2026-09-12

  • The app treats airplane mode, a disabled network adapter, low bandwidth, an unreachable Manage server or an expired login session as offline and carries on from local data.

    “Offline mode activates when devices are in "airplane mode," have "network adapter disabled," experience "low bandwidth," cannot reach "Maximo Manage," or when "login session expires." … continue to work …” — IBM Docs — Maximo Mobile authentication and data flow, read 2026-09-12

  • There is no offline switch to enable. The app moves between online and offline on its own.

    “There is no 'Enable Offline Mode' button in Maximo Mobile. It is designed in such a way that it automatically switches between Online and Offline mode based on the condition.” — IBM Support — How to enable Offline Mode in Maximo Mobile (17 Sep 2025), read 2026-09-12

  • After suite login the app holds a token for every server request: 30 minutes for the access token and 12 hours for the refresh token by default.

    “… a token, which is used to authenticate all requests to the server … 30 minutes for the access token and 12 hours for refresh token.” — IBM Docs — Maximo Mobile authentication and data flow, read 2026-09-12

Device requirements

  • Supported operating systems: Android 11 or higher, iOS 14.3 or higher, Windows 10 build 10.0.17763.0 or better, or Windows 11.

    “Android version 11 or higher, iOS version 14.3 or higher, or Windows 10 version 10.0.17763.0 or better, or Windows 11 operating system installed.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

  • Three gigabytes of memory is the floor; storage depends on how much data you download.

    “Minimum memory required is 3 GB. … Local storage varies based on the data volume expected to be downloaded from the server.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

  • Windows devices need the WebView2 Runtime.

    “Windows devices must include the WebView2 Runtime.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

  • Android devices need ARCore if you intend to run the Assist app.

    “Android devices must support ARCore if you intend to support the Assist application.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

  • Shared devices are the operating system's job: each user needs their own workspace and profile, and on iOS an MDM plus PIN or biometrics must be in place.

    “If the device is shared between users, the shared device is managed by the device operating system. Each user must have their own workspace and user profile. On iOS devices, to support device sharing, a mobile device management (MDM) solution must be installed on the device. PIN and biometrics must be available for authentication on the device.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

  • Keep device operating systems current, or the store app may stop being available to you.

    “Ensure that your devices and systems are updated with the latest operating system to make sure that you can continue to access the app store.” — IBM Docs — Device requirements for Maximo Mobile, read 2026-09-12

Getting the app onto devices

  • 9.0 introduced an MSIX installer for Windows, per user or per system.

    “A new MSIX installation program supports installing Maximo Mobile on Microsoft Windows on a per-user and per-system basis.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • On Windows an MDM such as Intune can push the server URL, whether users may change it, and Windows Hello, as an OMA-URI string.

    “You can configure Maximo® Mobile application settings by using a mobile device manager such as Microsoft Intune. … Create an Open Mobile Alliance Uniform Resource Identifier (OMA-URI) string that contains your Maximo Mobile application settings.” — IBM Docs — Configuring Maximo Mobile application settings on Windows with a mobile device manager, read 2026-09-12

Login, shared devices and security

  • Offline login and device authentication (PIN and biometrics) can be switched off with the disableofflinelogin and disabledeviceauthentication settings.

    “Disabling offline login and device authentication options includes disabling PIN and biometric authentication on a mobile device.” — IBM Docs — Disabling offline login and device authentication in Maximo Mobile, read 2026-09-12

  • E-signature keys work on the device from 9.0; 9.2 adds device biometrics for e-signatures.

    “Use e-signature keys in your web browser or your mobile device to confirm that a status change or attribute value update is complete and valid.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • An idle timeout for the mobile apps is a system property, maximo.mobile.userInteraction.idleTimeout.

    “The maximo.mobile.userInteraction.idleTimeout system property allows an administrator to set an idle session timeout value for Maximo Mobile applications.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

Data, sync and attachments

  • Since 9.0 a user can see how much storage the offline database, attachments, records and cache take, and view sync statistics and diagnostics.

    “You can review the amount of storage that is used by the offline database, attachments, application records, and cache. … You can review the statistics for data sync operations between the server and the mobile device.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • 9.0 lets you cap child records per parent and cap what the server returns for a query.

    “You can limit the number of child records that are downloaded to a device for parent records that are returned from a query. … Configure an application to limit the number of records that the server returns for a query.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • From 9.0 syncing one app also syncs its associated data; partial refreshes of work lists, supporting data and map data are independent.

    “Now, you can synchronize the data from an application and any associated data is also synchronized. … Partial updates make it possible to refresh work lists, supporting data, and map data independently.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

Administration and configuration

  • To confirm the Mobile level, read System Information (8.9 and later) or fetch /maximo/oslc/graphite/navigator/build.json and compare mobileVersion.

    “On Mobile 8.9 you can also confirm your interim fix level in the System Information by looking for 'IBM Maximo Mobile'.” — IBM Support — How to check your Maximo Mobile version? (24 Mar 2026), read 2026-09-12

The apps, release by release

  • 9.0: Quick Reporting on mobile, accept or reject assignments, optional enforced bar-code scanning before a status change, and technician location sharing.

    “Create new work orders quickly with a mobile version of the Quick Reporting application. … Before a technician starts a work order, they can accept or reject assignments that were defined as to be accepted. … Work orders can be configured so that technicians must validate the asset by scanning the bar code before changing the status of the work order.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • 9.0: calibration work orders with as-found and as-left readings, linear asset reference points, and Asset Configuration Manager removals, installs and switches.

    “Technicians are able to enter as-found (initial state) and as-left (final state) measurements and validate them against the tolerance limits. … Work orders can now access linear asset information, including reference points.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • 9.0: stage items, issue multiple items without a reservation, transfer between storerooms and create shipments from inventory usage records.

    “Stage items by using inventory usage records. … Add multiple inventory items without a reservation. … Create inventory usage records to transfer items between storerooms by using the mobile app. … Create shipments from inventory usage records by using the mobile app.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

  • 9.0 opens web links in the system browser and downloads inspection forms once at login.

    “Web links now open in the system browser. … Inspection forms are now downloaded once upon login, and then referenced by using lookup data.” — IBM Docs — What's new in Maximo Mobile 9.0, read 2026-09-12

Push notifications

  • Push notifications reach a device only while the Manage session is active, the user is signed in and the app has not been reset.

    “Push notifications are messages that are sent from the server to mobile devices when IBM® Maximo® Mobile application is being used. … Users receive push notifications only when their IBM Maximo Manage session is active, they are not signed out, and the Maximo Mobile app is not reset.” — IBM Docs — Configuring push notifications, read 2026-09-12

  • The push service is configured in the suite after Maximo Collaborate is deployed and activated from Manage, with an IBM ID API key and the bundle identifier com.ibm.iot.maximo.mobile.

    “After you deploy and activate Maximo® Collaborate from Maximo Manage, configure the push notification service in Maximo Application Suite so that the Maximo Collaborate feature works with your mobile service. … In the Bundle identifier field, specify com.ibm.iot.maximo.mobile.” — IBM Docs — Configuring push notification service for Maximo Collaborate, read 2026-09-12

Coming from Maximo Anywhere or 7.6.1

In your own tools

The same statements answer the maximo_mobile tool on the MCP server (scope by release and topic), and /api/mobile/facts serves them as JSON. Coming from Maximo Anywhere or 7.6.1? Start at the 7.6.1 → MAS 9.2 move and the deadlines.