Maximo Mobile: Anywhere is Dead and Your Field Teams Will Thank You

Who this is for: Maximo administrators, mobile architects, and field service managers who need to understand what replaces Maximo Anywhere in MAS 9 — and why your technicians are going to love it.

Estimated read time: 10 minutes

The Text You Never Want to Get

It is 7:14 AM. Your lead field technician texts you a screenshot. The Maximo Anywhere app on his iPad just crashed mid-inspection — the third time this week. He lost his findings. Again. He is standing in front of a boiler that needs a safety sign-off by noon, and he is writing readings on a paper towel because the app will not sync.

You know the drill. You remote into the MobileFirst server. You check the adapter logs. You confirm the Dojo framework is not throwing a rendering error on the custom inspection form you deployed last month. You ask him to clear the local database cache. He tells you, politely but firmly, that he is done with this app.

You have no good answer for him.

If this sounds familiar, you already know why Maximo Anywhere had to go. And if you are migrating to MAS 9, the replacement is not just an upgrade — it is a fundamentally different architecture that solves problems Anywhere was never designed to handle.

💀 Anywhere is Dead — Here is What Killed It

Let's be direct. Maximo Anywhere is not supported in MAS 9.0 or later. It is not deprecated with a grace period. It is not available as a compatibility option. It is gone.

And honestly? It needed to go.

Anywhere was built on IBM Worklight (later MobileFirst Platform), which was itself built on Apache Cordova. The UI layer used the Dojo Toolkit — a JavaScript framework that the broader industry moved away from years ago. Every customization required building and packaging native app bundles. Every update meant resubmitting to the Apple App Store and Google Play. Every inspection form download was a full payload transfer.

The architecture was a product of its era. It solved the offline problem for 2013. By 2024, it was solving yesterday's problem with yesterday's tools.

Hallway truth: "We spent more time managing the Anywhere build pipeline than we spent managing the actual inspections." — A mobile architect at a large utility company, explaining why they were first in line for the MAS 9 migration.

🔄 The Technology Shift: Anywhere vs. Mobile

Here is the comparison that matters. Every cell in this table represents a real pain point that Maximo Mobile addresses.

┌──────────────────────┬─────────────────────────────┬─────────────────────────────────┐
│ Aspect               │ Maximo Anywhere (7.6)       │ Maximo Mobile (MAS 9)           │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Technology Stack      │ IBM Worklight + Dojo        │ React.js on MAF                 │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Offline Support       │ Full offline + local DB     │ Full offline + optimized sync   │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Distribution          │ App store wrapping          │ PWA — no app store required     │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Updates               │ Rebuild & redeploy          │ Server-side updates             │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Inspection Forms      │ Downloaded per inspection   │ Downloaded ONCE at login        │
├──────────────────────┼─────────────────────────────┼─────────────────────────────────┤
│ Customization         │ XML config + custom adapters│ MAF Configuration application   │
└──────────────────────┴─────────────────────────────┴─────────────────────────────────┘

Let's unpack the ones that matter most to your daily operations.

React.js on MAF — Why It Matters

Maximo Mobile is built on React.js running on top of the Maximo Application Framework (MAF). This is not a cosmetic facelift. React is the most widely adopted UI framework in the world, which means:

  • Your development team can hire React developers instead of hunting for Dojo specialists who retired three years ago
  • The component model is modern, testable, and well-documented
  • Performance optimizations come from the React ecosystem, not from IBM-specific patches
  • MAF provides the Maximo-specific data layer — authentication, object structures, offline sync — while React handles the presentation

PWA Distribution — No More App Store Nightmares

This one changes everything for enterprise IT teams. Maximo Mobile is a Progressive Web App. Your technicians open a URL in their device browser. That is the deployment.

No Apple App Store review cycles. No Google Play submission process. No MDM-managed sideloading. No "the build broke because Xcode updated" conversations. No two-week delay between finishing a fix and getting it onto devices.

You push a server-side update. Every device picks it up on next launch. Done.

Inspection Forms Downloaded ONCE

In Anywhere, every time a technician opened an inspection, the form definition was downloaded from the server. For organizations running hundreds of inspections per day across dozens of form types, this was a performance bottleneck that directly impacted field productivity.

In Maximo Mobile, inspection form definitions are downloaded once at login and cached on the device. The technician opens an inspection and the form renders instantly from local cache. If you update a form definition on the server, it syncs at next login — not at every inspection open.

Key insight: For organizations with complex inspection programs — think utilities with 50+ form types, or oil and gas with nested conditional logic — this single change can save technicians minutes per inspection. Multiply that across hundreds of technicians and thousands of inspections per day, and you are recovering serious field hours.

📱 The Seven Mobile Apps

Maximo Mobile is not one app. It is seven purpose-built applications, each designed for a specific role. Here is the complete lineup.

┌─────────────────────┬─────────────────────────┬──────────────────────────────────────────────────┐
│ Mobile App          │ Target User             │ Key Capabilities                                 │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Technician          │ Field technicians       │ Accept/reject assignments, labor/materials,       │
│                     │                         │ GPS sharing, barcode scanning, e-signatures,      │
│                     │                         │ calibration WOs, offline work                     │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Asset Manager       │ Asset inspectors/mgrs   │ Asset data collection, condition assessment,      │
│                     │                         │ meter readings, field asset creation               │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Inspection Forms    │ Inspectors              │ Execute inspections, photos/signatures,           │
│                     │                         │ offline completion, cached form definitions        │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Issues & Transfers  │ Storeroom clerks        │ Issue inventory, transfer between storerooms,     │
│                     │                         │ tools transfer, shipment creation                  │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Inventory Receiving │ Receiving clerks        │ Receive against POs, inspect on receipt,          │
│                     │                         │ quantity validation, put-away assignment            │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Inventory Count     │ Count personnel         │ Physical counts, cycle counts, barcode-driven,    │
│                     │                         │ multi-bin, count approval workflow                  │
├─────────────────────┼─────────────────────────┼──────────────────────────────────────────────────┤
│ Service Request     │ All users / self-service│ Create SRs, attach photos, view status,           │
│                     │                         │ rich text descriptions, map-based creation          │
└─────────────────────┴─────────────────────────┴──────────────────────────────────────────────────┘

Each app installs independently. Your technicians do not need the Inventory Count app. Your storeroom clerks do not need the Technician app. This is role-based mobile — deploy only what each user needs.

🔧 Technician App Deep Dive

The Technician app is the flagship. It is where your field workforce lives, and IBM has loaded it with capabilities across MAS 9.0 and 9.1.

MAS 9.0 Features

Assignment Management
Your technicians can accept or reject assignments before starting work. This sounds simple, but in Anywhere, the workflow for declining an assignment was clunky enough that most organizations just told technicians to ignore work orders they could not do. Now there is a clean accept/reject flow built into the assignment card.

Calibration Work Orders
If you run calibration programs, Mobile supports calibration-specific work orders with as-found and as-left measurement validation. The technician records measurements on the device, and the system validates tolerance ranges before allowing completion.

GPS Location Sharing
This is configurable — and that matters for organizations with unions or privacy policies. When enabled, technician locations are periodically sent to the server and displayed on dispatcher maps.

The system property that controls this:

maximo.mobile.locationssharing.enabled=1

When this property is set to 1, the Technician app shares GPS coordinates at configurable intervals. Dispatchers see technician locations on the Graphical Assignment map. When set to 0, no location data leaves the device.

Hallway truth: "We had three months of union negotiations before we could turn on GPS sharing. The fact that it is a single system property we can toggle — instead of a device-side code change — made the conversation much easier." — A maintenance manager at a transit authority.

Barcode Scanning Enforcement
You can require technicians to scan an asset barcode before changing work order status. This eliminates the "worked on the wrong pump" scenario that every maintenance organization has experienced at least once.

Electronic Signature Enforcement
For regulated industries — pharma, food processing, nuclear — electronic signature capture is enforced on status changes. The technician signs on the device screen, and that signature is stored with the work order record.

Quick Reporting
Technicians can create work orders directly in an in-progress state for emergency or unplanned work. No need to go through the full work order creation workflow when you are standing in front of a broken asset.

Server-Side Search
Searches execute on the server, not on the local device database. This means search results reflect current data, not just the subset that was synced to the device.

Partial Data Refresh
The sync engine only transfers changed records, not the full dataset. If your technician has 200 work orders synced and 3 changed since last sync, only those 3 are updated.

Linear Asset Support
For infrastructure maintenance — pipelines, roads, rail lines — the Technician app supports linear reference points so technicians can identify the exact segment they are working on.

Material Request Creation
Technicians can create material requests from the field. No more calling the planner to ask for parts.

MAS 9.1 Enhancements

MAS 9.1 adds capabilities that dispatchers and supervisors have been requesting since Mobile launched.

Self-Assign from Work Queue
Technicians can browse a work queue and assign work to themselves. This is transformative for organizations that use a pull-based model instead of push-based dispatch. The technician closest to an asset pulls the next job instead of waiting for a dispatcher to assign it.

Unassign and Reassign Accepted Work
In 9.0, once a technician accepted an assignment, it was locked to them. In 9.1, they can unassign themselves or reassign to a colleague. This handles the real-world scenario where a technician gets halfway to a site and gets pulled to an emergency.

View Asset Work History in the Field
Technicians can now view the work order history for an asset while standing in front of it. No more calling back to the office to ask "what was done on this pump last time?" The history is right there on the device.

Configure Start-Travel Display
Regardless of GPS distance calculation, you can configure when the start-travel button appears. This addresses edge cases where GPS accuracy inside large facilities made the automatic distance trigger unreliable.

Auto-Stop Timers
When a technician starts a new work order, any running timer on a previous work order automatically stops. No more forgotten timers inflating labor hours.

Follow-Up Work Orders
Create follow-up work orders from the field with the applicable asset and location pre-populated. The technician finishes a PM, notices something else needs attention, and creates a follow-up without re-entering asset data.

📋 Service Request Mobile

The Service Request app deserves separate attention because it serves a different audience — not just maintenance professionals, but potentially every employee in your organization.

MAS 9.0 Capabilities

  • Rich text formatting with hyperlinks in descriptions
  • Attachment renaming with file name and description customization
  • Web link opening in system browsers
  • Photo attachment from camera or gallery

MAS 9.1 Additions

Service Request Duplication
Users can duplicate an existing service request. For recurring issues — "the same light is out again in Building C" — this saves significant data entry time.

View Others' Requests
Users can see service requests created by other people. This reduces duplicate submissions. Before you create a request for a broken elevator, you can check if someone already reported it.

Create from Maps
Users can create service requests directly from a map interface by tapping a location. This is particularly powerful for facility management scenarios where users may not know the formal Maximo location hierarchy but can point to where the problem is on a floor plan.

📦 Inventory and Receiving Mobile

Three apps cover the storeroom and receiving workflows.

Issues and Transfers

  • Stage items for issue
  • Issue inventory items with or without reservations
  • View and edit charge information
  • Transfer items between storerooms
  • Create shipments for transfers
  • Tools transfer with or without reservations
  • Reference work orders, material requests, or internal purchase orders

Inventory Count

  • Barcode-driven counting — scan items instead of typing part numbers
  • Cycle count support
  • Multi-bin counting
  • Count approval workflow
  • Count reconciliation (online only — this is not available offline)

That last point matters. If your counters work in areas with no connectivity, they can perform the count offline, but reconciliation must happen when they are back online.

Receiving

  • Receive against purchase orders
  • Inspection on receipt
  • Quantity validation
  • Put-away location assignment

🔌 Offline Sync: How It Actually Works

Offline capability was the defining feature of Maximo Anywhere, and it remains central to Maximo Mobile. But the implementation is fundamentally different.

What Downloads to the Device

When a technician logs in, the sync engine downloads a scoped dataset to the device. This is not the entire Maximo database — it is a configurable subset relevant to that user:

  • Their assigned work orders
  • Related assets and locations
  • Applicable inspection form definitions (downloaded once, remember)
  • Lookup data for dropdowns and picklists
  • Storeroom inventory relevant to their assignments

The data scope is configurable. You control how much data goes to each device, which directly impacts sync time and device storage consumption.

Sync Strategy

┌──────────────────────────────────────────────────────────────┐
│                    OFFLINE SYNC FLOW                         │
├──────────────────────────────────────────────────────────────┤
│                                                              │
│  LOGIN ──→ Full scope download ──→ Forms cached              │
│                                                              │
│  WORKING OFFLINE:                                            │
│    ├── Complete work orders                                  │
│    ├── Record labor and materials                            │
│    ├── Run inspections                                       │
│    ├── Scan barcodes                                         │
│    └── Changes queued locally                                │
│                                                              │
│  CONNECTIVITY RESTORED:                                      │
│    ├── Partial sync (changed records only)                   │
│    ├── Conflict detection                                    │
│    ├── Server-side resolution                                │
│    └── New assignments downloaded                            │
│                                                              │
│  SUBSEQUENT SYNCS:                                           │
│    └── Delta only — not full payload                         │
│                                                              │
└──────────────────────────────────────────────────────────────┘

Conflict Resolution

What happens when a technician changes a work order offline, and someone in the office changes the same work order on the server? Maximo Mobile uses server-side conflict resolution. When the device syncs:

  1. The system detects the conflict (same record modified in both places)
  2. Server-side rules determine which change wins
  3. The technician is notified if their change was overridden
  4. A conflict log is maintained for audit purposes

This is a significant improvement over Anywhere, where conflict handling was inconsistent and often resulted in silent data loss.

Storage Management

Maximo Mobile manages device storage actively. If a device is running low on storage, the sync engine can reduce the cached dataset. Administrators can configure maximum storage thresholds per app to prevent devices from running out of space during field operations.

⚙️ Customization via MAF Configuration

Here is where the operational model changes most dramatically for your mobile team.

In the Anywhere world, customizing a mobile app meant:

  1. Editing XML configuration files on a development workstation
  2. Building the app bundle using MobileFirst CLI tools
  3. Testing on emulators and physical devices
  4. Packaging for app store deployment
  5. Submitting to Apple/Google for review
  6. Waiting days to weeks for approval
  7. Pushing the update through MDM to devices
  8. Hoping the update did not break something only visible on a specific device model

In the Maximo Mobile world:

  1. Open the MAF Configuration application in the Maximo web UI
  2. Make your configuration change
  3. Save

That is it. The change applies to all devices on their next app load. No builds. No app store. No MDM push. No device-specific testing matrix.

Key insight: The MAF Configuration application is server-side. Your mobile administrator configures the apps from a desktop browser. Changes propagate through the standard sync mechanism. This means you can have one person managing mobile configuration for thousands of devices, and changes roll out in hours instead of weeks.

What can you configure through MAF? Field visibility, field ordering, default values, business rules, data sources for lookups, and app navigation. What you cannot do through MAF is build entirely new screens or add custom React components — that requires IBM-provided extension patterns or custom development with IBM's SDK.

🗺️ The Migration Path: Anywhere to Mobile

If you are currently running Maximo Anywhere, here is what the transition looks like at a high level.

What Transfers

  • Business processes — your work order flow, inspection logic, and approval chains are server-side and do not change
  • Data — all work order, asset, and inspection data stays in Maximo
  • Security model — mobile security groups and access controls carry forward
  • Integration points — server-side integrations are unaffected

What Does Not Transfer

  • Anywhere customizations — XML configurations and custom adapters do not migrate. You will rebuild customizations in MAF Configuration
  • Custom Anywhere apps — if you built custom mobile apps on the Worklight framework, they must be re-implemented
  • Device-side code — any JavaScript or Dojo customizations deployed to devices are gone
  • App store presence — your enterprise Anywhere app listing in the app store is no longer needed

The Hard Truth

There is no automated migration tool from Anywhere to Mobile. Your Anywhere customizations will be rebuilt, not migrated. The good news is that most Anywhere customizations exist because the base app was missing functionality that Mobile now provides natively. Start by mapping your Anywhere customizations against Mobile's out-of-the-box features — you may find that 60-80% of what you customized is now standard.

Hallway truth: "We had 47 Anywhere customizations. When we mapped them against Maximo Mobile's feature list, 31 of them were covered out of the box. The remaining 16 took us three weeks in MAF Configuration. Our Anywhere custom development had taken eight months." — A solutions architect at a mining company.

📊 The Bottom Line for Your Organization

Here is the before-and-after that your leadership needs to see.

┌───────────────────────────┬──────────────────────┬──────────────────────┐
│ Metric                    │ Anywhere             │ Mobile               │
├───────────────────────────┼──────────────────────┼──────────────────────┤
│ Time to deploy update     │ 2-6 weeks            │ Hours                │
│ App store dependency      │ Yes                  │ No (PWA)             │
│ Inspection form load time │ Every open           │ Once at login        │
│ Custom dev framework      │ Dojo (obsolete)      │ React.js (dominant)  │
│ Offline support           │ Yes                  │ Yes (improved sync)  │
│ Build infrastructure      │ MobileFirst Server   │ None (server-side)   │
│ Device-side testing       │ Per device model     │ Browser-based (PWA)  │
│ Conflict resolution       │ Inconsistent         │ Server-side rules    │
└───────────────────────────┴──────────────────────┴──────────────────────┘

The operational cost reduction is significant. You eliminate the MobileFirst server infrastructure. You eliminate the app build pipeline. You eliminate the app store management overhead. You eliminate the device-specific testing matrix. And you gain a configuration model that lets one administrator manage mobile experiences for thousands of users.

Key Takeaways

  • Maximo Anywhere is dead — not deprecated, not optional, not available as a compatibility layer. It is gone in MAS 9, replaced entirely by Maximo Mobile built on React.js and the Maximo Application Framework
  • PWA deployment eliminates the app store bottleneck — no builds, no submissions, no MDM pushes. Users open a URL and they are running the latest version
  • Seven purpose-built apps cover the complete field workflow — Technician, Asset Manager, Inspection Forms, Issues and Transfers, Receiving, Inventory Count, and Service Request
  • MAS 9.1 transforms field autonomy — self-assign from work queues, unassign and reassign accepted work, and view asset work history without calling the office
  • Inspection forms download once at login — not per inspection. For high-volume inspection programs, this single change recovers measurable field hours
  • Offline sync is smarter — partial data refresh, configurable data scope, server-side conflict resolution, and active storage management
  • MAF Configuration replaces device-side customization — server-side changes apply to all devices automatically. No rebuilds, no redeployments, no weeks-long update cycles
  • GPS sharing is a system property toggle — maximo.mobile.locationssharing.enabled=1 enables it, and your privacy/union conversations are simpler when it is a server-side switch instead of a code change

References

Series Navigation:

Previous: Part 4 — Graphical Scheduling and Dispatching
Next: Part 6 — Security Model and Map Features

View the full MAS FEATURES series index -->

Part 5 of the "MAS FEATURES" series | Published by TheMaximoGuys

Maximo Anywhere served its purpose for a decade. It brought offline field work to Maximo when nothing else could. But the technology stack aged out, the deployment model became a bottleneck, and the customization approach could not keep up with modern expectations. Maximo Mobile is not just Anywhere with a fresh coat of paint — it is a ground-up rebuild that changes the economics of mobile maintenance. Your field teams are going to notice the difference on day one.