Maximo Mobile in MAS 9.1: A Field Technician's Operating Manual
# Maximo Mobile in MAS 9.1: A Field Technician's Operating Manual
The MAS 9.1 release is the most significant update to Maximo Mobile in years. For field technicians, the experience has been rebuilt around clearer status transitions, faster offline workflows, and the kind of contextual intelligence that turns a phone in a pocket into a real-time extension of the back office. For mobile administrators, the configuration model has been simplified in ways that reduce the per-deployment effort.
This article is a practical operating manual for both audiences. It walks through what is new, how the pieces fit together, and where the configuration landmines are.
The MAS 9.1 Mobile Experience: What Is New
The 9.1 release builds on the foundation that MAS 9.0 established. The four highest-impact changes for field technicians are:
1. A new dispatching status model that gives dispatchers and planners real-time visibility into where a technician is in the lifecycle of an assignment.
2. Rotating asset support that lets technicians track, audit, and update serialized equipment in the field.
3. Server-side work order search that delivers faster, more accurate results, especially in large enterprises.
4. A new HSE Incident Reporter for health, safety, and environment incidents, with photo and GPS capture built in.
Each of these is a meaningful capability on its own. Together, they change the rhythm of the technician's day. A technician who leaves the depot with a stack of work orders can now see exactly which job is highest priority, update the dispatching status as they travel, audit rotating assets on the way, and report a safety incident without leaving the app. The result is a workflow that requires fewer context switches and less time wrestling with the technology.
The New Dispatching Status Model
In MAS 9.1, the single Assignment Status has been split into two coordinated status dimensions: the existing Assignment Status and a new Dispatching Status. The result is a more granular lifecycle that the dispatcher can monitor in real time.
The new status values map as follows:
| Assignment Status | Dispatching Status |
|-------------------|--------------------|
| ASSIGNED | ASSIGNED, DISPATCHED, RECEIVED, ACCEPTED |
| STARTED | TRAVELLING, ONSITE, STARTED, RESTORED |
| COMPLETED | COMPLETED |
| CANCELED | CANCELED |
The practical effect is that a dispatcher can see not just that a work order has been started, but that the technician is currently travelling, on site, or actively working. This is the difference between a status field that says "in progress" and a workflow that says "left the depot, parked at the site, opened the job plan."
From the technician's perspective, the change is mostly positive. The mobile UI surfaces the new states with distinct icons. MAS 9.0 introduced separate icons for starting work versus starting travel, and MAS 9.1 extends that visual language to the new dispatching states. The result is a UI that communicates state at a glance, which matters when a technician is in a noisy substation with gloves on.
The configuration model is also worth understanding. The new statuses are managed through the standard Assignment Status domain, and the new Cron Task that calculates travel times between service addresses depends on the new status values to do its work. If you customize the assignment lifecycle, plan to update the cron task configuration as well.
A practical tip: the most common configuration mistake with the new dispatching statuses is to leave the cron task at its default cadence. The cron task calculates travel times every 15 minutes by default, which is too infrequent for a busy dispatch team. Tune the cadence to match your operational tempo, and monitor the cron task history to confirm the calculations are running.
Rotating Assets: A New Mobile Workflow
Rotating assets, equipment that moves between locations or roles, have always been a configuration headache. A pump that belongs to a construction crew today and a maintenance team tomorrow needs to be tracked in motion, and the mobile app is the natural place to do it.
MAS 9.1 introduces first-class support for rotating assets in Maximo Mobile. Technicians can now:
- View rotating asset details in the field, including current location, status, and condition.
- Audit assets to confirm they are where they should be.
- Update asset records in real time when a piece of equipment moves.
- Track serialized equipment accurately across multiple jobs.
The audit capability is the most operationally significant addition. A field audit, where a technician walks a route and confirms that each piece of equipment is in its expected location, used to require a separate paper or spreadsheet process. It now lives in the mobile app, with the data flowing back to Manage in near real time.
The configuration is straightforward: rotating assets are enabled at the asset class level, and the mobile app will display the relevant fields automatically. There is no custom development required for the basic workflow. If you need to extend the audit with custom fields, the standard Maximo Application Framework (MAF) configuration tools apply.
A useful pattern is to schedule rotating asset audits as preventive maintenance activities. A monthly walk-down audit becomes a routinized part of the maintenance program, with the results captured in the mobile app and visible to the reliability team in Manage. The combination of audit data and work order history is a powerful input to the asset health scoring model.
Server-Side Work Order Search
In MAS 9.0, Maximo Mobile introduced server-side search for work orders. Instead of relying on records that had been downloaded to the device, technicians could now search the Manage database directly. The results were stored on the device so they remained available in disconnected mode.
MAS 9.1 expands this capability. The technical team can now configure additional data sources to use the same server-side search pattern, which means the same fast, accurate search that technicians enjoy for work orders is available for other data sources. The configuration is done through the Mobile Configuration application in the suite administration UI.
For large enterprises with thousands of work orders, the performance improvement is dramatic. A search that returned after a 30-second wait on a downloaded dataset can return in under a second against a properly indexed server. The change is most visible in environments where technicians were filtering large lists of downloaded work orders manually.
The trade-off is that the configuration must be set up correctly. If the server-side search is misconfigured, technicians will see incomplete results. The most common mistake is not configuring the field-level index on the search object. Without the index, the server falls back to a full table scan and the search is slower than the offline version.
A useful diagnostic is the Mobile Diagnostics screen, which shows the search latency and the index status for each data source. If a search is slower than expected, the Diagnostics screen will tell you whether the index is in use.
The New HSE Incident Reporter
Health, safety, and environment incidents are time-critical. The faster a near-miss is reported, the more useful the data is, and the more likely the organization is to act on it. MAS 9.1 introduces a dedicated HSE Incident Reporter in Maximo Mobile.
The reporter allows field staff to:
- File an incident report directly from the device.
- Attach photos, descriptions, and GPS coordinates.
- Trigger escalation workflows automatically.
The integration with the back office is the most important part. An incident reported in the field appears in the standard Maximo incident management workflow within seconds, where the safety team can take ownership. The data flow is one-way during the report, but once the incident is in the back office, the full Maximo incident lifecycle applies.
The HSE reporter is delivered as a separate mobile app module, which means it can be deployed to a subset of users. A configuration team can choose to enable it for all technicians, or only for those who have completed the relevant safety training. The user management and security group configuration in MAS 9.1 make this kind of targeted deployment straightforward.
A useful pattern is to integrate the HSE reporter with the work order system. An incident report can trigger an automatic work order for the safety team, which closes the loop between reporting and remediation. The integration is configured through the standard Maximo automation scripts, and it is a good first project for teams that are new to MAS automation.
Offline Data Management: Tighter Controls
MAS 9.0 introduced several performance improvements for offline use, including a configurable limit on the number of child records downloaded and partial data updates that refresh only what has changed. MAS 9.1 builds on these with central management of preloaded database content and query limits.
The configuration surface for an administrator now includes:
- Preloaded database management. Specify which records are preloaded to the device. The preloaded database determines what is available offline. With MAS 9.1, the management of this content is centralized in the Mobile Configuration application.
- Query limits and filters. Define how many records are synced to mobile devices for each data source. The default limits are sensible for most deployments, but very large enterprises often need to tune them.
- Active user identification. See which users are currently logged into the mobile app, which is invaluable for support and for license reconciliation.
The configuration model is one of the quiet wins of MAS 9.1. In earlier releases, mobile configuration lived in multiple places, and a change to a query limit required a redeployment. The centralized model means changes can be tested in a staging environment and promoted to production with a single configuration update.
A useful diagnostic is the Mobile Performance screen, which shows the data download size and duration for each user. If a particular technician is consistently downloading more data than their peers, it usually means their preloaded database has grown beyond what is sensible. A targeted cleanup of the preloaded content can dramatically improve their app performance.
Calibration Updates That Technicians Will Notice
For organizations that use Maximo Manage's calibration module, MAS 9.1 introduces a set of small but meaningful improvements in the mobile app:
- Additional remarks on data sheets. Calibration engineers and technicians can now add, edit, and view nonconformance notes directly on the data sheet, which makes the regulatory record more complete.
- Anchored calibration header. The calibration header is now anchored at the top of the screen, so technicians do not lose their place as they scroll through calibration points.
- Status visible immediately after save. After saving calibration values, the technician can see the final status without navigating away. The workflow becomes more conversational and less of a data-entry chore.
- Background synchronization of safety plan reviews. When a technician reviews a safety plan associated with a work order, the review is recorded with a timestamp automatically.
The calibration changes are not headline features, but
...
