Maximo Mobile 9.1: The Offline-First Future of Field Maintenance

Maximo Mobile 9.1: The Offline-First Future of Field MaintenanceField maintenance technicians have always been the hardest users to serve with enterprise asset management systems. They work in remote locations, inside steel structures, underground, and in facilities with unreliable network connectivity. They need access to work orders, asset histories, safety procedures, inspection forms, and parts catalogs, and they need all of it available instantly, sometimes without any network connection at all. IBM Maximo Mobile 9.1 is IBM's answer to this challenge, and it represents a fundamental rethinking of how field technicians interact with Maximo.

Maximo Mobile replaced Maximo Anywhere as the mobile strategy for MAS. It is a single application that runs on iOS, Android, and Windows, works in both online and offline mode, and provides role-based access to work execution, inspections, and inventory capabilities. There is no separate mobile license required for MAS. The app is configured through Mobile Studio, a low-code development environment within MAS, and it leverages device-native capabilities including voice-to-text, camera capture, barcode scanning, GPS location, and electronic signatures.

This article covers the Mobile 9.1 architecture, the technician experience, the new assignment and work order management features, the inspection and inventory capabilities, the centralized administration tools, and the migration path from Maximo Anywhere or MobileFirst-based solutions.

The Offline-First REST and Sync Architecture

The defining characteristic of Maximo Mobile 9.1 is its offline-first architecture. Unlike previous mobile solutions that treated offline mode as a fallback, Mobile 9.1 is designed to operate primarily offline, syncing with the server when connectivity is available. This approach ensures that technicians always have access to their work, regardless of network conditions.

The architecture consists of three layers: the mobile device running the Maximo Mobile app, the Mobile Application Server (MAS) that mediates between the device and Maximo Manage, and the Maximo Manage application that serves as the system of record. The mobile app stores data locally in a SQLite database on the device, with a sync engine that handles bidirectional data exchange with the server.

The sync process works on a delta model. When the device connects to the server, it sends any locally modified records (work order status changes, meter readings, inspection results, material issues) and receives any server-side changes (new work orders, updated assignments, revised job plans). The sync is incremental: only changed records are exchanged, not the full dataset. This minimizes data transfer and reduces sync time, which is critical for technicians who may have only brief windows of connectivity.

{
  "syncProfile": {
    "name": "Field Technician Standard",
    "preloadQueries": [
      {
        "object": "WODETAIL",
        "whereClause": "status in ('APPR','INPRG') and assignee = :user",
        "maxRecords": 50,
        "orderBy": "wopriority asc, schedstart asc"
      },
      {
        "object": "ASSET",
        "whereClause": "assetid in (select assetid from wodetail where status in ('APPR','INPRG') and assignee = :user)",
        "maxRecords": 100
      },
      {
        "object": "ITEM",
        "whereClause": "itemnum in (select itemnum from wpmaterial where wonum in (select wonum from wodetail where status in ('APPR','INPRG') and assignee = :user))",
        "maxRecords": 200
      }
    ],
    "syncInterval": 300,
    "conflictResolution": "SERVER_WINS"
  }
}

Conflict resolution is a critical design decision in offline architecture. When a record is modified on both the device and the server between syncs, the system needs a rule to determine which version wins. Mobile 9.1 supports configurable conflict resolution policies: server wins (the server version overwrites the device version), client wins (the device version overwrites the server version), or manual resolution (the conflict is flagged for a supervisor to review). The most common production configuration is server wins for master data (assets, locations, job plans) and client wins for transactional data (work order status, meter readings, inspection results), since the technician's on-site observations are the most current.

The preloaded database is another key concept. When a technician first logs in, the app downloads a configured set of data: assigned work orders, relevant assets, job plans, safety procedures, inspection forms, and parts catalogs. This data is available immediately, even before the first sync. Administrators can configure the preload queries in Mobile Studio to control what data each role receives, how much data is downloaded, and how often it refreshes.

Security in the offline context is handled through role-based access control (RBAC) that is enforced on the device. When a user logs in, their security profile is downloaded and cached locally. All data access on the device is filtered through this profile, ensuring that technicians can only see the assets, work orders, and applications they are authorized for, even when offline. If a user's security profile changes on the server, the updated profile is applied at the next sync.

The Technician Experience: Work Orders, Assignments, and Reporting

The technician experience in Maximo Mobile 9.1 is built around the work order lifecycle: receive, accept, travel, execute, report, and complete. Each step has been streamlined in 9.1 to reduce friction and give technicians more control over their work.

Work order assignment management is significantly enhanced in 9.1. Technicians can now reassign or unassign work orders even after accepting them. This addresses a long-standing frustration: a technician accepts a work order, arrives on site, and discovers that the job requires a different skill or that the asset is in a different location. Previously, the technician had to call a dispatcher to reassign the work. Now they can do it directly from the mobile app, and the dispatcher sees the change in real time.

The ability to revise accepted work assignments is another 9.1 addition. Technicians can reject previously accepted assignments (with a reason code) or mark them as complete. This gives technicians more agency over their work queue and ensures that the dispatching system has accurate status information.

The Start Travel button, which records travel time to the work site, can now be configured to display regardless of the GPS distance from the site. Previously, the button only appeared when the technician was within a certain radius. In 9.1, administrators can configure it to always show, allowing technicians to record travel time in scenarios where GPS is unreliable (underground, inside large facilities, in urban canyons).

Meter readings have been improved in several ways. Technicians can add remarks to meter readings, providing context that goes beyond the numeric value. When connected to the server, the last meter reading is fetched before the meter reading page opens, ensuring that the technician sees the most recent reading and can enter a delta or actual value accordingly. For continuous meters, the app clearly indicates whether an actual or delta reading is required, reducing data entry errors.

Follow-up work order creation is streamlined. Technicians can create follow-up work orders directly from the multiple asset and location section of the work order, choose which assets and locations the follow-up applies to, and delete irrelevant options. This is particularly useful for inspection-driven maintenance, where a single inspection may identify issues on multiple assets that each require separate corrective work orders.

Labor reporting in 9.1 is more flexible. Technicians can edit internal or external labor transactions that are not automatically approved, correct mistakes in labor hours, and report premium labor hours (overtime, hazard pay, shift differentials) directly from the Report Work page. This reduces the administrative burden on supervisors who previously had to correct labor transactions after the fact.

Inventory, Assets, and Inspections on Mobile

Maximo Mobile 9.1 extends beyond work execution into inventory management, asset management, and inspections, making it a comprehensive tool for field operations.

For inventory, technicians can now select an asset and choose from the list of items defined as spare parts for that asset when issuing materials to a work order. This is a significant improvement over the previous approach, which required technicians to search for part numbers manually. The app displays the part description, available quantity in the storeroom, and bin location, making it easy for technicians to find and issue the correct parts.

Attachment handling is substantially improved in 9.1. Technicians can select and upload multiple attachments in a single flow, with the flexibility to modify attachment details (description, file type, document folder) before uploading. Support for large files has been expanded: mobile users can now upload and download attachment files up to 200 MB in size from iOS and Android devices. This enables technicians to attach high-quality inspection photos, lengthy video walkthroughs, and detailed schematic drawings to work orders.

For asset management, 9.1 adds the ability for technicians to create and edit asset classifications from their mobile device. Technicians can create rotating assets (assets that are themselves inventory items, like spare motors or tools) directly from the mobile app, including scanning the asset's barcode to populate the asset number and tag. This is particularly valuable for field operations where new assets are installed or commissioned on site.

Inspections on mobile have been streamlined with the multiple assets and locations table now accessible at the line level. This means that during a multi-asset inspection, the technician can work through each asset's inspection questions without navigating back to a parent record. The inspection form rendering on mobile supports all question types, conditional logic, scoring, and electronic signatures, providing full parity with the desktop inspection experience.

// Mobile Studio: Custom action to check stock availability before issue
function checkStockBeforeIssue(context, action) {
  const itemnum = context.page.data.ITEM.ITEMNUM;
  const storeloc = context.page.data.ITEM.LOCATION;

context.callAction('MXAPIINVENTORY', 'checkStock', { itemnum: itemnum, storeloc: storeloc }).then(function(result) { if (result.available The calibration history view on mobile now shows up to 20 records by default, giving technicians visibility into an asset's calibration history while in the field. This is important for regulated environments where technicians need to verify that an asset's calibration is current before performing work.

Centralized Mobile Administration

Mobile administration in MAS 9.1 introduces centralized management tools that give administrators visibility and control over the mobile deployment. This is a significant improvement over previous versions where mobile administration was fragmented across multiple tools.

The centralized mobile administration console allows administrators to identify mobile logged users, see which devices are active, what apps they are running, and when they last synced. This is valuable for troubleshooting: if a technician reports that they cannot see new work orders, the administrator can check whether the device has synced recently and whether the user's preload queries are returning results.

Administrators can also administer mobile settings, queries, and the preloaded database from the central console. Changes to preload queries (adding new object structures, changing where clauses, adjusting max records) can be deployed without requiring an app rebuild. The settings are pushed to devices at the next sync, ensuring that all users have consistent configurations.

Push notification support has been extended in 9.1 to include background data synchronization. Previously, push notifications were primarily for alerts: new work order assigned, inspection overdue, PM reminder. In 9.1, push notifications can trigger background sync, so when a new work order is assigned, the device automatically syncs to download the work order details, job plan, and associated data. When the technician opens the app, the work is already available, with no waiting for a sync to complete.

Extended push notification support also includes the ability to send targeted notifications to specific user groups. A dispatcher can send a notification to all technicians working on a specific site, or a supervisor can notify all team members about a safety alert. The notifications are delivered through the standard iOS and Android push notification infrastructure, ensuring timely delivery.

The device location sharing feature, introduced earlier and refined in 9.1, allows technicians' GPS locations to be shared with dispatchers. This is opt-in and can be configured per role. The dispatcher sees technician locations on a map in the Dispatching dashboard, enabling more efficient assignment decisions. The location is updated periodically (configurable interval) and only while the app is active, addressing privacy concerns.

Migration from Maximo Anywhere and MobileFirst

For organizations currently using Maximo Anywhere or MobileFirst-based custom mobile solutions, the migration to Maximo Mobile requires a planned transition. The two architectures are fundamentally different: Anywhere was a hybrid application framework that used MobileFirst as the middleware, while Mobile 9.1 is a native app with a REST-based sync engine integrated directly into MAS.

The migration approach depends on the complexity of the current mobile solution. Organizations using out-of-the-box Maximo Anywhere applications (Technician, Inventory, Inspections) with minimal customization can migrate relatively quickly. The standard workflows in Mobile 9.1 cover most of the same functionality, and the improved user experience typically results in faster adoption.

Organizations with heavily customized Anywhere applications face a more complex migration. Custom Anywhere applications built on the MobileFirst framework cannot be directly ported to Mobile 9.1. They need to be rebuilt as Mobile Studio app definitions, which involves redefining the data sources, UI layout, and actions in the Mobile Studio environment. This is an opportunity to revisit the customizations and determine whether the standard Mobile 9.1 capabilities can replace them, reducing ongoing maintenance burden.

The recommended migration approach is parallel running: deploy Mobile 9.1 alongside the existing solution, pilot it with a small group of technicians, validate the workflows and data, and then progressively move users to the new app. The old solution can remain available during the transition period to handle edge cases or workflows that have not yet been migrated.

Training is a critical success factor. The Mobile 9.1 interface is significantly different from Anywhere, and technicians who have used the old app for years need structured training to transition effectively. Focus training on the common workflows (accept work, navigate to site, complete work order, report labor, submit) and provide quick reference guides for the most frequent tasks.

Practical Implications

For organizations already on MAS, Mobile 9.1 is a significant upgrade that addresses many of the limitations of earlier mobile releases. The assignment management, meter reading improvements, and large file support are high-value features for field operations. The centralized administration tools reduce the operational overhead of managing a mobile deployment.

For organizations migrating from Maximo 7.6, Mobile 9.1 is a fresh start. The Anywhere-based mobile solution from 7.6 is end of life, and Mobile 9.1 is the strategic mobile platform. Plan the mobile migration as a parallel workstream to the core MAS migration, with its own training, testing, and rollout schedule.

The offline-first architecture means that the preloaded database configuration is one of the most important design decisions. If the preload is too large, initial login takes too long and consumes excessive device storage. If it is too small, technicians will not have the data they need when offline. Start with a conservative preload configuration, test with real technicians in real field conditions, and iterate based on feedback.

Bottom Line

Maximo Mobile 9.1 is the most capable mobile solution IBM has delivered for Maximo, and it is the strategic mobile platform for all MAS deployments. The offline-first architecture, combined with the comprehensive work order, asset, inventory, and inspection capabilities, provides technicians with everything they need to work effectively in the field. The centralized administration and Mobile Studio configuration tools give administrators the control they need without the complexity of the old MobileFirst platform. For any organization serious about field maintenance, Mobile 9.1 is not optional. It is the future of how technicians interact with Maximo.