📊 Maximo Mobile Meter Reading
📖 Introduction
Meter readings in IBM Maximo are critical for monitoring asset health, tracking usage, and triggering preventive maintenance. With Maximo Mobile, technicians can capture these readings in the field, improving efficiency and reducing delays.
This blog explores what changed in Maximo Mobile 9.1 compared to 9.0, the new features introduced, and how you can customize them to fit your business needs.
⚠️ Meter Reading in Maximo Mobile 9.0
Limitations
❌ Readings not shared across work orders: Example: Two work orders (WO1 and WO2) linked to the same asset (e.g., a centrifugal pump with meters like pressure and run hours). If a user entered a new pressure reading in WO1, it did not reflect in WO2.
❌ No support for remarks or delta readings: Users couldn't add comments or specify whether a reading was delta or actual.
❌ Offline-created work orders lacked meter data: Work orders created offline didn't have associated asset meters available for entry. Technicians had to reconnect and revisit work orders just to populate meter readings—counterintuitive for a true offline workflow.
❌ Data fragmentation and performance issues: Meters were child data of work orders via the activeassetmeter.mxapiassetmeter relationship. Each work order, task, or MultiAssetLocations record downloaded its own meter set, causing duplicate data downloads, slower API performance, and stale readings when updates occurred elsewhere.
🚀 Meter Reading in Maximo Mobile 9.1 — A Complete Revamp
Maximo Mobile 9.1 represents a major leap forward in how meter readings are handled. The functionality has been revamped in terms of efficiency, features, performance, and data integrity, addressing many limitations from previous versions. In this section, we will explore these changes in detail and include technical insights that can help you understand the current implementation better—especially if you plan to customize this area for your business needs.
Before diving into the new features, it's important to understand the architectural restructuring that underpins these improvements. In version 9.0, meters were treated as child data of work orders, which meant they were segregated and duplicated across multiple records. This design caused inefficiencies, stale data, and performance bottlenecks.
In 9.1, meter reading is now implemented as a common component shared across multiple applications, with its own unified data structure. Meters are no longer tied to individual work orders; instead, they are linked directly to Assets and Locations, aligning mobile functionality with Maximo's core architecture. This change ensures consistency and eliminates duplication, making meter data a single source of truth across all applications.
🔧 From a technical perspective:
For Assets, the mobile app uses the MXAPIASSET object structure and the int_assetmeter relationship.
For Locations, it uses MXAPIOPERLOC and the int_locationmeter relationship.
In simple terms, meters are now associated with Assets and Locations, not work orders. This restructuring improves data integrity, enables cross-app sharing, and lays the foundation for advanced features like offline meter availability and delta readings.
✨ New Features in 9.1
1️⃣ Meters Available Offline
One of the most significant improvements in Maximo Mobile 9.1 is the ability to enter meter readings even when a work order is created offline. This enhancement addresses a major pain point from version 9.0, where technicians had to reconnect to the network and revisit work orders just to populate meter readings—a process that disrupted workflow and defeated the purpose of a true mobile solution.
💡 How It Works
In 9.1, as long as Asset and Location meter data is available in the mobile database, users can record readings for work orders created in disconnected mode.
This means technicians can complete their tasks without worrying about connectivity, improving efficiency in remote or low-network environments.
❓ What Assets and Meters Are Available Offline?
This is a critical question because Maximo environments can have millions of assets, and downloading all of them to a mobile device is impractical due to storage and performance limitations.
To balance functionality and performance, Maximo Mobile uses saved queries to determine which assets and their meters are downloaded for offline use.
⚙️ Default Behavior
Technician app downloads assets linked to the default Assigned Work list. Saved query: ASSIGNEDWOASSETWITHMETERS Defined under MXAPIASSET
Asset Manager uses the query: ASSETWITHMETERS covers assets from the default My Assets list.
with offline-immediate-download=true, this ensures these assets and their meters are downloaded during mobile app initialization and remain available offline.
Result: Users can create new work orders for these assets and enter meter readings without reconnecting.
🎨 Customization Options
One size does not fit all. Organizations can adjust saved queries to suit their business needs and optimize download performance. For example:
If you have a limited set of assets, you can use a broader query: MOBILEASSETWITHMETER and MOBILELOCATIONWITHMETER This downloads all active Assets and Locations from your Maximo environment.
⚠️ Known Limitations
For environments with large asset volumes, downloading all assets for both Technician and Asset Manager applications can impact performance.
Careful planning is required to balance offline usability with data download size.
🛠️ How to Implement Customization
- For Technician Application:
- For Assets - Alter the "ASSIGNEDWOASSETWITHMETERS" saved query of "MXAPIASSET" object structure
- For Locations – Update "ASSIGNEDWOLOCATIONWITHMETERS" saved query of "MXAPIOPERLOC" object structure
- For Asset Manager Application:
- For Assets - Alter the "ASSETWITHMETERS" saved query of MXAPIASSET object structure
- For Locations – Alter the "LOCATIONWITHMETERS" saved query of "MXAPIOPERLOC" object structure
2️⃣ Refresh Readings from Server
In addition to offline capabilities, Maximo Mobile 9.1 introduces a feature that is particularly useful in connected environments: Refresh Meter Readings. This functionality allows users to pull the latest meter readings from the server before entering new data, ensuring that they are working with the most accurate and up-to-date information.
The refresh feature is critical for preventing data conflicts. For example, if multiple technicians are working on the same asset, one technician's update could overwrite another's if the local data is outdated. By refreshing readings from the server, users can confirm the current values before recording changes, reducing errors in delta calculations and improving overall data accuracy.
The process is simple: a Refresh button is available on the meter readings screen. When tapped, the application calls the Maximo server to retrieve the latest meter values and updates the local mobile database accordingly. These capabilities provide a robust solution for maintaining accurate meter data in both connected and disconnected scenarios.
Refresh button on meter readings screen
3️⃣ Delta Reading and Remarks Field
One of the most notable enhancements in Maximo Mobile 9.1 is the introduction of Delta Reading capability. Previously, users could only enter actual readings, which represent the total accumulated value of a meter (e.g., total run hours or total distance traveled). While this works for some use cases, many organizations prefer to record incremental changes—such as hours since the last maintenance or distance traveled since the last reading. This is where delta readings become essential.
With 9.1, users can now toggle the Only Delta option when entering a meter reading. This toggle is implemented through the isDelta property in the mobile application, allowing the system to interpret the reading as an incremental value rather than an absolute one.
In addition to delta readings, Maximo Mobile 9.1 introduces a Remarks field. This field allows technicians to add contextual information when updating a meter reading, such as "Current ODOM at location" or "Pressure spike observed during operation." The remarks field is configurable in terms of maximum length, giving organizations flexibility to meet their documentation standards. It's important to note that remarks can only be entered when a reading is being updated, ensuring that comments remain relevant and tied to actual changes.
Delta reading toggle and remarks field
4️⃣ Cross-App Data Sharing
Before version 9.1, meter readings were siloed within individual work orders, tasks, or MultiAssetLocations records. This caused significant challenges for organizations that rely on accurate and consistent data across multiple applications. For example, if a technician updated a meter reading in the Technician app, that change was not immediately visible in the Asset Manager app or other related applications. This lack of synchronization often led to discrepancies, stale data, and redundant work.
Maximo Mobile 9.1 addresses this issue by restructuring meter data to reside at the Asset and Location level, rather than being tied to individual work orders. This architectural change ensures that meter readings are shared across all applications that reference the same asset or location. As a result, when a technician updates a meter reading in one application, the updated value is instantly available in other applications, such as Asset Manager.
This improvement delivers several benefits. First, it enhances data integrity by eliminating duplicate or outdated readings. Second, it provides real-time visibility, ensuring that managers and technicians are working with the most current information. Finally, it streamlines workflows by removing the need to manually refresh multiple work orders or applications. From a technical perspective, this is achieved through shared data architecture leveraging MXAPIASSET and int_assetmeter for assets, and MXAPIOPERLOC and int_locationmeter for locations, aligning mobile functionality with Maximo Manage's core design.
📊 Comparison Table: 9.0 vs 9.1
| Feature |
Version 9.0 |
Version 9.1 |
| Offline created Workorder Meter Entry |
❌ Not supported |
✅ Supported with new saved queries |
| Delta Reading |
❌ Not available |
✅ Available with toggle |
| Remarks Field |
❌ Not available |
✅ Available |
| Cross-App Data Sharing |
❌ No |
✅ Yes |
| Refresh from Server |
❌ No |
✅ Yes |
| Data Structure |
Child of Work Order |
Child of Asset/Location |
❗ Common Issue: "Record not available in the device" Error
Why am I getting "Record not available in the device" Error When Opening the Meter Dialog?
This is a common question among Maximo Mobile users, and the answer lies in how meter data is retrieved for offline and online operations. When you see the error "Record not available in the device", it means that the asset or location you are trying to access is not part of the saved query used for meter data download. In other words, the mobile application does not have the required asset or location in its local database because the saved query does not include it.
🤔 Why Does This Happen?
Maximo Mobile relies on saved queries to determine which assets and locations are downloaded for offline use. If your asset is not included in the query definition, the mobile app cannot display its meters.
✅ The Solution: Enhancement in Patch 9.1.11
This issue has been completely resolved in patch 9.1.11 with a significant enhancement that addresses the limitation in both Role-Based Applications (RBA) and Mobile applications.
🔧 RBA Enhancement:
In RBA, this issue is now completely fixed. Users can enter meter readings for any asset, regardless of whether it's included in the saved query. The application now seamlessly fetches asset meter data from the server when needed, eliminating the "Record not available in the device" error entirely in web-based workflows.
📱 Mobile Enhancement:
For mobile users, patch 9.1.11 enable a way to use: "Refresh meter readings". Instead of error toast of "Record not available in the device", you will see "Asset not available" message and if you're online, you can now tap the "Refresh meter readings" button to fetch the asset and its meters directly from the server.
This means that even if your saved query didn't include the asset you want to add meter readings for, you can still access it by refreshing. The application will retrieve the asset meters data from the server and make it available for meter entry, providing flexibility without requiring changes to your saved queries.
Key Benefits:
- No need to modify saved queries to include every possible asset
- On-demand access to any asset when connected online
- Maintains offline efficiency while providing online flexibility
- Consistent user experience across RBA and Mobile platforms
💡 Note: This enhancement was introduced in Maximo Mobile patch 9.1.11. If you're experiencing the "Record not available in the device" error, ensure you're running patch 9.1.11 or later to take advantage of this improvement.
🎯 Conclusion
Maximo Mobile 9.1 introduces significant improvements to meter reading functionality, making it more efficient, consistent, and user-friendly. Features such as offline meter availability, delta readings, remarks field, cross-app data sharing, and refresh from server collectively enhance the technician experience and align mobile workflows with Maximo's core architecture.
However, as with any major enhancement, these changes come with their own challenges. One of the key concerns is duplicate data downloads—both across different applications and within the same application for transactional and lookup data. This can impact performance and storage, especially in environments with large asset volumes. These challenges are being actively considered for future improvements to optimize meter reading capabilities even further.
I will keep this document updated with the latest developments and solutions as these improvements evolve. Stay tuned for updates on how these challenges are being resolved and additional best practices for customization.
Other Resources:
Maximo Mobile - Performance optimization