Assetize

Maximo Mobile desk

Maximo Mobile 9.1, 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.1

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

  • From 9.1 the Windows app comes only from the Microsoft Store.

    “Starting in Maximo Mobile 9.1, the IBM® Maximo Mobile app for Windows is available only from the Microsoft store.” — IBM Docs — What's new in Maximo Mobile 9.1, 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

  • Shared-device setups on 9.1 or later must set up local authentication so offline users can log in.

    “Starting in Maximo® Mobile 9.1, in environments that require users to share mobile devices, administrators must configure Maximo Mobile to enable offline users to log into Maximo Mobile by using local authentication.” — IBM Docs — Disabling offline login and device authentication in Maximo Mobile, read 2026-09-12

  • 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

  • 9.1 lets an administrator mark a device as shared from the container settings page.

    “You can designate a mobile device as a shared device by enabling the Shared device option from the Container settings page.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • From 9.1 administrators choose which browser handles login on browsers and devices.

    “Starting in version 9.1, administrators can specify which browser can be used to log in from browsers and mobile devices.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1 can refuse spoofed GPS positions from devices and emulators.

    “Configure Maximo Mobile to prevent mobile devices and emulators from reporting false GPS location information.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

Data, sync and attachments

  • From 9.1 a login refreshes the device from the server automatically.

    “When you log in to Maximo Mobile, your device is automatically refreshed with updated data from the server.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1 delta sync can carry more of the child data on transactional records.

    “You can configure Maximo Mobile to deliver more details about child data contained in transactional data records during a synchronization of delta information.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • Preloaded databases can be generated per site or language and handed to those users (9.1); 9.2 lets you configure, monitor and stop their generation.

    “Preloaded databases can be generated and distributed to users assigned to specific sites, or language.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • Attachments up to 200 MB move to and from iOS and Android devices from 9.1; multiple attachments upload in one flow.

    “Mobile users can now upload and download attachment files from their iOS and Android devices that are up to 200 MB in size. … You can now select and upload multiple attachments in a single flow with the flexibility to modify the attachment details.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1 moved image libraries to ImgLib and a cron task that sizes and transfers them over OSLC.

    “Maximo Mobile v9.1 now uses ImgLib and a utility class cron task to control the transfer and sizing of image libraries through OSLC.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

Administration and configuration

  • The Mobile Configuration app arrived in 9.1 as the one place suite administrators configure the mobile apps; 9.2 moves the Maximo Mobile properties into it.

    “The Mobile Configuration app provides a centralized place for Suite administrators to manage the configuration of mobile apps.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • What a sync refreshes on the device is set in the Mobile Admin app (9.1).

    “Use the Mobile Admin app to configure the data that is refreshed on mobile devices when a sync operation is initiated.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • From 9.1 Manage and the suite count the users who have access to the mobile apps.

    “The number of users with access to Maximo Mobile apps can be tracked in Maximo Manage and Maximo Application Suite.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • Priority and work type for work orders raised from Quick Reporting on a device are system properties (maximo.mobile.Priority and its work-type sibling); sr.mobile.sapriority picks the service-address object.

    “Use the maximo.mobile.Priority system property to configure the priority of work orders that are created by using Quick Reporting on mobile devices. … Use the sr.mobile.sapriority property to designate which object to reference for the service address.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • Log cache can be cleared in the app from 9.1; 9.2 saves Android log files to a folder you choose.

    “Log files cache can now be cleared from the app, which allows for faster uploads and improves the support experience.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 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.1: create a work order from a long-press on the map, filter by scheduled date, reassign or unassign after accepting, timers that stop automatically, classify work orders, and audit assets.

    “Technicians can create a work order using GIS coordinates on their mobile device by long-clicking on a location on the map. … Technicians can now reassign or unassign work orders even after accepting the work. … Work order timers can be configured to automatically stop when a technician starts the timer in another work order.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1: report co-workers' labor, premium pay, edit unapproved labor, actual quantities for tools, and pick spare parts from the asset.

    “Technicians can now report the labor of their co-workers. … Technicians can now enter labor premium pay from the Report work page for labor. … When technicians need to issue a spare part in a work order, they can now select an asset and choose from the list of items that are defined as spare parts for the asset.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1: inspection photos can be analysed automatically by Maximo Visual Inspection models.

    “If you have IBM Maximo Visual Inspection, you can configure inspections to automatically analyze images using MVI models.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1: duplicate, reference and follow service requests, raise one from the map, and hide or show high-priority ones by signature option.

    “You can duplicate a service request record from the service request details page from a mobile device. … You can create a service request from a map by long pressing on any point in the map. … You can choose to hide or show high priority service requests using a signature option in the Security Groups application.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1: loop-location calibration, printed calibration labels, calibration points added during execution, standard deviation for repeatable points, and 20 records of asset calibration history.

    “Calibration technicians can now be assigned loop location based calibration work orders. … When completing a preventive maintenance calibration work order, technicians can generate and print calibration labels. … Technicians can now view up to 20 records for any asset in the calibration history in Maximo Mobile by default.” — IBM Docs — What's new in Maximo Mobile 9.1, read 2026-09-12

  • 9.1: storeroom clerks create rotating assets on the device, issue and transfer tools like items, and update receiving bins.

    “Storeroom clerks can now create rotating assets from their mobile device. … Issue and transfer tools from inventory in the same way that items are transferred. … Receiving bins and additional attributes can be updated upon receipt.” — IBM Docs — What's new in Maximo Mobile 9.1, 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.