Maximo Mobile and Field Service in MAS 9.2: The Connected Technician

Maximo Mobile and Field Service in MAS 9.2: The Connected TechnicianField service management has always been the sharp end of asset management. It is where plans meet reality, where schedulers in an office try to match technicians in trucks to problems in the field, and where the quality of your data and tools determines whether a job takes two hours or four. IBM Maximo Application Suite 9.2, released in June 2026, brings the most significant set of mobile and field service improvements the platform has seen. AI is now embedded in the technician's daily workflow, scheduling has become conversational, and the gap between the field and the back office is narrower than it has ever been.

This article covers what is new in Maximo Mobile and Field Service Management (FSM) in MAS 9.2, what changed from 9.1, and what implementation teams need to know to deploy these capabilities successfully. We will walk through the AI-powered Maximo Assistant on Mobile, conversational scheduling and what-if analysis, Visual Inspection with on-device inference, the expanded offline capabilities, the HSE incident reporter, and the centralized mobile administration console. For each capability, we will cover what it does, how it works under the hood, and what it means for your field operations.

Maximo Assistant on Mobile: Natural Language in the Field

The Maximo Assistant on Mobile is the most visible AI feature in the 9.2 release for field technicians. It allows technicians to use natural language to find asset information, review work order history, and complete work efficiently. Instead of navigating through multiple applications and search screens, a technician can type or speak a question: "Show me the maintenance history for pump P-301" or "What were the last three work orders on boiler B-12?" The assistant returns the relevant information in a conversational interface, with links to drill down into specific records.

Under the hood, the assistant uses a retrieval-augmented generation (RAG) architecture. It queries the Maximo Manage database through standard APIs, retrieves the relevant records, and uses a language model to compose a natural language response. The response includes direct links to the underlying Maximo records, so the technician can jump from the assistant's answer to the full work order or asset record with a single tap. The assistant is aware of the technician's security context, which means it only returns information the technician is authorized to see.

The practical impact is significant. Technicians often spend 15 to 20 minutes per job searching for asset history, reviewing previous repairs, and understanding the context of the current work. The assistant compresses that into seconds. For new technicians who do not have years of institutional knowledge about which assets have chronic issues and what repairs have been attempted, the assistant provides instant access to the same information that experienced technicians carry in their heads.

A deployment consideration: the assistant requires connectivity to the Maximo server. It does not work in fully offline mode, because the RAG architecture needs to query the database in real time. If your technicians work in areas with poor connectivity, they should use the assistant when online to gather context before going offline to complete the work. IBM has indicated that offline assistant capabilities are on the roadmap but not available in 9.2.

Conversational Scheduling and What-If Analysis

On the back-office side, MAS 9.2 introduces AI-enabled conversational scheduling and what-if analysis for planners, schedulers, and field service managers. This feature allows schedulers to explore scenarios using natural language instead of manually adjusting assignments and running calculations.

A scheduler can ask: "What if I add two more technicians next week?" or "What happens if I prioritize the pump overhaul at Plant 3 over the scheduled PMs?" The system applies the organization's constraints and business rules to the query and returns optimized assignment options. It considers technician availability, skill qualifications, travel time, inventory availability, and work order priority. The scheduler can then accept, modify, or reject the proposed changes.

This is a meaningful shift from the manual, spreadsheet-driven scheduling that most field service organizations still rely on. In a typical MAS 8.x environment, a scheduler spends 30 to 40 percent of their day on what-if analysis: manually reassigning work orders, recalculating travel times, checking skill availability, and trying to optimize the schedule. Conversational scheduling compresses this into a few minutes per scenario.

The what-if analysis is not just about adding resources. It can also model the impact of removing resources (sick calls, vacation), changing priorities (emergency work displacing planned work), or shifting schedules (moving a PM from Tuesday to Thursday). The system shows the projected impact on key metrics like first-time fix rate, SLA compliance, and technician utilization.

A practical consideration: the conversational scheduling feature needs clean data to produce useful results. If your technician skill records are incomplete, your travel time estimates are inaccurate, or your work order priorities are inconsistent, the what-if analysis will produce recommendations that look good on paper but fail in practice. Before enabling this feature, invest in cleaning up your labor records, ensuring skill qualifications are current, and validating that your work order priority scheme reflects actual business priorities.

Maximo Visual Inspection: AI on the Device

Maximo Visual Inspection in MAS 9.2 introduces AI-based visual inspection with local inference directly on the mobile device. This means a technician can point their phone camera at an asset, and the device runs a trained model to identify defects, wear patterns, or compliance issues without sending the image to a server for processing.

Local inference is a critical capability for field operations. Many industrial sites have poor or no network connectivity in the field. Traditional cloud-based image recognition requires uploading the image and waiting for a response, which is impractical when you are standing next to a compressor in a remote location. With local inference, the model runs on the device, and the result is available in seconds.

The use cases span industries. A technician inspecting a pipeline can point the camera at a weld and the model identifies potential corrosion patterns. An electrician can photograph a breaker panel and the model verifies that the correct breakers are installed. A facilities team can scan a roof and the model identifies damaged tiles. The models are trained using Maximo Visual Inspection's training pipeline, which allows subject matter experts to upload labeled images and train custom models without data science expertise.

A deployment pattern: start with a single inspection type and a small set of assets. Train the model with 200 to 500 labeled images. Deploy the model to a pilot group of technicians. Measure the model's accuracy (true positive rate) and false positive rate in the field. A true positive rate above 80 percent is a good starting point. Below that, add more training images or narrow the scope of the inspection. Once the model is performing well, expand to additional asset classes and inspection types.

Expanded Offline Capabilities and Mobile Improvements

Maximo Mobile has supported offline operations since its introduction, but MAS 9.1 and 9.2 have significantly expanded what technicians can do without a network connection. Understanding the offline model is essential for any organization with field workers in remote locations.

The offline architecture works by preloading data to the device before the technician goes offline. The administrator configures which data is preloaded: work orders assigned to the technician, assets in their work area, spare parts inventory, inspection forms, and relevant job plans. The technician works in the field, creating and updating records offline. When connectivity is restored, the device synchronizes the changes with the server.

In MAS 9.1, the offline capabilities were expanded with several key improvements. Technicians can now reassign work orders even after accepting them, providing flexibility when field conditions change. They can revise accepted work assignments, rejecting or completing them as needed. Meter readings were improved with the ability to add remarks and see the last reading fetched from the server before the meter reading page opens. Follow-up work orders can be created directly from the mobile device, including the ability to choose which assets and locations the follow-up work applies to. Labor hours can be edited and premium labor hours reported directly from the Report Work page.

In MAS 9.2, these capabilities are complemented by the broader AI features. The push notification system has been extended to support background data synchronization, which means the device can sync data even when the mobile app is not actively open. This reduces the time technicians spend waiting for data to sync when they come back online. Support for large files up to 200 MB means technicians can upload and download long videos, high-quality images, and large documents from their iOS and Android devices.

The centralized mobile administration console, introduced in 9.1 and enhanced in 9.2, gives administrators a single pane of glass for managing the mobile deployment. Administrators can see which users are actively logged into Maximo Mobile, manage preloaded databases for offline usage, define query limits and filters for syncing records, and deploy mobile configurations to user groups. This centralized model supports enterprise-wide consistency in how mobile apps are used and managed, which is critical for organizations with hundreds of field technicians across multiple regions.

HSE Incident Reporter and Safety Workflows

A standout addition to the mobile suite is the HSE (Health, Safety, and Environment) Incident Reporter, which enables immediate reporting of safety incidents in the field. Technicians can attach photos, GPS locations, and descriptions directly from their mobile device. The incident is escalated through the organization's defined workflow, triggering the appropriate response.

In MAS 9.2, this capability has been expanded with AI-assisted incident classification. When a technician creates an incident report, the system suggests categories based on the description and identifies similar events. This improves the consistency and completeness of safety reporting, which is critical for regulatory compliance and for identifying patterns that might indicate systemic safety issues.

The expanded safety capabilities in 9.2 go beyond incident reporting. Field teams can complete inspections and initiate permit-to-work processes directly from a mobile device. Contractor safety oversight has been improved, and asset-centric waste management capabilities have been added. These features connect safety and compliance more directly to daily operations, rather than treating them as separate processes that happen in parallel.

The practical impact is that safety data becomes more accurate and more timely. Incidents reported in real time with photos and GPS coordinates are far more useful than incidents reported on paper forms days after the fact. And when safety data is in the same system as work order data, the organization can identify correlations between maintenance activities and safety events, which is the foundation of a data-driven safety program.

Practical Implications

The mobile and field service capabilities in MAS 9.2 represent a significant step forward, but they require deliberate implementation. The AI features (Assistant, conversational scheduling, visual inspection) need clean data and careful pilot testing. The offline capabilities need thoughtful configuration of preloaded data to balance device storage with field needs. The safety workflows need integration with existing safety processes and regulatory requirements. Organizations that invest in these areas will see measurable improvements in first-time fix rates, technician productivity, and safety data quality. Organizations that deploy the features without preparation will find that AI recommendations are only as good as the underlying data and that offline mode is only useful if the right data is preloaded.

Bottom Line

Maximo Mobile in MAS 9.2 is not just a upgrade. It is a redefinition of what field service management looks like in an asset-intensive organization. The combination of AI-powered assistant, conversational scheduling, on-device visual inspection, expanded offline capabilities, and integrated safety workflows creates a toolkit that was not available in any single product before. For organizations currently on MAS 8.x or 9.0, the mobile improvements alone justify the upgrade to 9.2. For organizations still on Maximo 7.6 with the old Maximo Everyplace or Mobile First, the difference is transformative. The connected technician is no longer a concept on a roadmap. It is a deployable reality.