Maximo Mobile 9.2 Field Toolkit: Inspections, Inventory, QR Codes, Crew Management, and Geofencing in Practice

For most of its life, Maximo Mobile was a work-order execution surface. A technician opened the app, saw their assigned WOs, navigated to the asset, completed the work, recorded labor and materials, and closed the WO. That is still the core loop, but MAS 9.2 — and the Mobile 9.2 feature channel updates — turn it into a full field toolkit. The technician can now do inspections, count and transfer inventory, scan QR codes, manage a crew, and use geofencing to drive location-aware work assignment, all from the same app, with the same offline-first execution model.

This article walks through each of those capabilities as it actually works in the 9.2 release train, with the configuration patterns that the most experienced mobile teams use.

The Mobile 9.2 capability map

The Mobile 9.2 feature set breaks into five practical capability groups:

1. Inspections and asset data capture — Mobile Inspections, condition assessment, image and video capture, AI-assisted defect classification
2. Inventory and material handling — barcode/QR scanning, inventory counts, transfers, kit management, issue-to-WO
3. Crew and location-based work — crew visibility, role-based task assignment, geofencing, location-based WO routing
4. Failure reporting and task execution — structured failure codes, multi-failure reporting, conditional task flows
5. Offline-first execution — local DB, conflict resolution, sync on reconnect, the same model that has worked since 8.x but now with deeper coverage

Let me walk through each.

Inspections and asset data capture

The Mobile Inspections application in Mobile 9.2 supports four inspection patterns:

• Asset inspection — periodic asset-by-asset walk-down, with question/answer forms, photo capture, and conditional questions based on previous answers.
• Route inspection — location-by-location walk-down for linear assets (substations, pipelines, conveyor systems, road networks), with sequential routing and exception-only reporting.
• Safety inspection — checklist-driven, with mandatory photo evidence and signature capture.
• Condition-based inspection — driven by a meter's threshold breach. When a sensor reading crosses a configured threshold, an inspection record is auto-generated, routed to the responsible crew, and tracked through to completion.

The 9.2 release added two practical improvements:

• AI-assisted defect classification. The technician takes a photo, the image is sent to Maximo Visual Inspection (MVI) for inference, and the MVI model returns a defect class and a confidence score. The technician confirms or overrides. The defect class lands in the inspection record and the failure code hierarchy. This is the integration pattern that the MVI team has been pushing for the last 18 months, and it is now a documented, supported pattern.
• Video capture for asset condition. Photo capture was always supported; video is new. The use cases are visual inspection of complex assets (transformers, switchgear, large rotating equipment) and "show me what you saw" attachments for the work order history.

The pattern that works for inspections is to build the inspection form in the Maximo Manage Inspection Form application first, then publish it to Mobile. The form, the question set, the conditional logic, and the failure class mapping all live in Manage. Mobile reads the form definition and renders it. A change to the form in Manage is reflected in Mobile on the next sync, with no Mobile app update required.

Inventory and material handling

Mobile 9.2 is the first release where inventory is a first-class Mobile workflow rather than a desktop-side activity that the technician calls in. The four core workflows are:

• Inventory count — a cycle count, a physical inventory, or a spot count. The technician navigates to the storeroom, scans bins and items, and the system records the count. Variance from the on-hand quantity is calculated server-side and surfaces as a count variance report.
• Inventory transfer — moving stock between storerooms (a service van, a lay-down yard, a sub-bin) using the Mobile transfer workflow. The transfer generates an inventory transfer record and updates on-hand quantities on both storerooms on sync.
• Kit management — pre-assembled kits (a "PM kit" for a specific job plan, a "tool kit" for a specific crew) that the technician checks in and out. The kit is tracked as a single asset with child items.
• Issue-to-WO — the technician scans a barcode or QR code, the system identifies the item, and the issue-to-WO workflow posts the material against the active work order. This is the workflow that closes the loop between inventory and work execution.

The 9.2 release added native QR-code scanning for both assets and materials. The barcode scanner is built into the Mobile camera pipeline, so no third-party scanner app is required. The QR code can resolve to:

• An asset (scan to navigate to the asset record)
• A location (scan to navigate to the location and see child assets)
• A PM (scan to see the PM record and start a work order)
• A work order (scan to navigate to the active WO)
• A part (scan to see the inventory record and issue to a WO)
• A document (scan to open an attached manual, drawing, or procedure)

The QR-code pattern is the single biggest field-execution improvement in years for a specific class of user: the technician who works the same set of assets and locations every day and previously had to navigate the asset tree in Mobile to find what they were looking for.

Crew and location-based work

The 9.2 release turned crew management in Mobile from "we have an assigned owner group" to a real crew concept:

• Crew record — a defined crew with a lead, members, skills, equipment, and current assignment. The crew is visible on the Mobile dispatch board and the Manage Crew application.
• Crew lead visibility — the crew lead sees a board of their crew's work for the day, can reassign tasks, can flag WO completion for review, and can see where each crew member is (geofencing-driven, with the technician's consent).
• Crew-based work assignment — a planner can assign a WO to a crew (not a person), and any qualified member of the crew can pick it up in Mobile. This is the pattern that has worked in the Maximo Scheduler for years, now surfaced cleanly in Mobile.
• Crew as a scheduling unit — the Mobile dispatch board shows crew availability in real time, with shift, location, and skill filters.

The 9.2 release added geofencing as a first-class field service feature. A geofence is a polygon defined in the Spatial or Mobile configuration that triggers an action when a device enters or exits the polygon. The patterns that work:

• Auto-arrive on WO — when the technician's device enters the geofence of the asset's location, the WO status auto-transitions to INPRG (in progress) with a timestamp. No more "I forgot to start the WO" complaints.
• Auto-complete on WO — when the device exits the geofence, the WO can be auto-completed, or a "are you done?" prompt can be surfaced.
• Location-based WO routing — the Mobile dispatch board can sort WOs by distance from the technician's current location, with the geofenced assets showing as a sorted list.
• Asset tracking — for high-value mobile assets (a test cart, a portable analyzer, a rental generator), the asset's location can be tracked via the device's geofenced position and the location history is recorded against the asset record.

Geofencing requires the technician's consent for location tracking. The Mobile app surfaces the consent prompt on first use, and the technician can revoke it at any time. The consent status is recorded in the audit log.

Failure reporting and task execution

The 9.2 Mobile release did not change the failure reporting model in a radical way, but it tightened three things that matter at the field level:

• Multi-failure reporting. A single work order can now record multiple failures (a pump with a seal leak, a bearing fault, and a vibration anomaly). The failures are recorded as a list within the WO, each with its own failure class, cause, and remedy. This is the pattern that matches how a technician actually thinks about a problem asset.
• Conditional task flows. A job plan can have conditional tasks (e.g., "if the oil sample shows particle count > X, perform task Y"). The conditional logic is evaluated in Mobile as the technician progresses through the job plan, and the conditional tasks appear or hide in real time.
• Failure history lookup. When the technician is reporting a failure on an asset, the Mobile app surfaces the asset's failure history (the last 10 failures, with their classes, causes, and remedies) so the technician can see what has happened to this asset before and apply the same remedy if appropriate.

The offline-first execution model

The 9.2 Mobile release did not change the offline-first architecture, but it extended it to the new capabilities:

• Inspections are offline-first. The inspection form definition is synced to the device, and the inspection data is stored locally on the device until it syncs. A technician can do a full day's inspections with no connectivity.
• Inventory counts and transfers are offline-first. The bin and item data is synced to the device, the count is recorded locally, and the variance is calculated server-side on sync. Transfers between storerooms are local-only until the device is back in connectivity.
• Geofencing is offline-first. The geofence polygons are synced to the device, and the enter/exit events are recorded locally. The server-side action (auto-arrive, auto-complete, location update) is triggered on sync.
• QR-code resolution is offline-first. The QR-code-to-entity mapping is synced to the device, so a scan resolves to the asset, location, or work order even with no connectivity. The mobile app shows a stale-data warning when the entity has not been synced in the last N hours.

The offline-first model is the reason Mobile works for utilities, mining, oil and gas, and rail. The 9.2 release extended the model to every new capability, which is what made the new feature set usable in the field rather than just in the office.

The configuration that holds the toolkit together

All of the new Mobile 9.2 capabilities are configured in Maximo Manage and pushed to Mobile on sync. The configuration surfaces are:

• Mobile configuration (Mobile Configuration application) — what objects, fields, and applications are exposed to Mobile. The 9.2 release added new object structures for Inspections, Inventory, and Crew.
• Inspection forms (Inspection Form application) — the question/answer forms, conditional logic, and failure class mapping. The form is the unit of inspection configuration.
• Geofence definitions (Geofence application, or via the Spatial application) — the polygon definitions, the actions, and the device consent policy.
• Crew configuration (Crew application) — crew records, members, skills, and equipment.
• QR-code configuration (QR Code application, or via the URL handler in Manage) — the QR-code-to-entity mapping and the resolved entity view in Mobile.

The right way to ship a Mobile 9.2 rollout is to enable one new capability at a time, train the technicians, observe the field behavior, and tune. A "big bang" rollout of all five new capabilities in a single change is the path to a confused field force. A staged rollout — inspections first, then inventory, then QR codes, then crew, then geofencing — is the path to adoption.

The biggest predictor of Mobile 9.2 success is not the configuration, it is the training. A field force that does not know what geofencing does for them will turn off the consent prompt. A field force that has been walked through the QR-code-to-asset flow will use it 50 times a day. Plan the training as carefully as the configuration.