All learning series · Transition guide · Part 1
Anywhere to Mobile transition
Inventory existing field processes and validate their replacement explicitly.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Anywhere to Mobile transition? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use an Anywhere to Mobile transition?
Anywhere is the application you are leaving. Maximo Mobile is the client on MAS. Readiness here is an inventory of the Anywhere work plus the Mobile course’s checks. MAS 9.x does not include Anywhere as the target.
Before configuration
List every Anywhere application, what it saves, and whether Mobile has a place for that save. Entitle Mobile, not Anywhere, on the suite.
Before the first successful journey
One frequent technician task that already works in Mobile, online, with the same business result as the Anywhere screen.
Before production use
Custom Anywhere behaviour has a destination: Mobile configuration, a supported extension, or a retired step. Cut over one task at a time.
Licensing, entitlement and AppPoints
The MAS 9.2 licensing guidance includes Maximo Mobile at Limited, Base and Premium, with Limited use inside three modules. It does not list Maximo Anywhere as a MAS 9.2 application, and this course does not treat Anywhere as entitled on the suite. Third-party mobile that still updates Maximo-owned records needs a user entitlement. Apple and Google accounts are third-party. Use the Mobile readiness rows for the client you are moving to, and keep this page as the inventory of what must move.
Keep four facts separate for Maximo Mobile as the replacement client. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Mobile is the installed client to verify. Anywhere remains on the 7.6.1.x system you are leaving until that task has moved. Installed, for the target, means the Mobile client connects to the MAS workspace. The source Anywhere environment is still required until the last task has a destination.
Foundation configuration
The Manage records the technician already uses — work, asset, location, labor, assignment — have to exist on the target before the device can show them. Custom fields and actions from Anywhere are the gap list. They are not automatically on the Mobile screen.
Product configuration
For each Anywhere screen, name the Mobile screen or the gap. Move one task through Mobile configuration. Do not start by rebuilding every customisation. Review offline behaviour against the task, using the Mobile course’s offline row.
Infrastructure and integration
Devices need the Mobile route, TLS and the store build. Anywhere’s old middleware is retired with the task, not before the new path works. Push and device management are the same third-party items as in the Mobile course.
Data and operational readiness
The first journey is one real task: the same work order updated from Mobile and read back in Manage, with the result the Anywhere user expects. A missing field on the Mobile screen is a gap in the inventory. A refused login is the Mobile tier. A record that only exists in Anywhere is data that still has to move.
Setup order for the move
- 1. Inventory the Anywhere tasks Screens, fields, actions, offline use.
- 2. Entitle and install Mobile Follow the Mobile readiness checks. Anywhere is not the MAS client.
- 3. One task online The business result matches, and Manage shows the update.
- 4. Then the next task Including offline only where the task needs it.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Mobile entitlement, not an Anywhere entitlement on MAS | The target client is Mobile, at Limited, Base or Premium. This course does not entitle Anywhere on MAS 9.x. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage. The Mobile course. | Technicians on the Mobile tier they need, including the three-module limit if they are Limited. | Read the tier. Confirm you are not looking for an Anywhere install line on the 9.2 table. | The project waits for an Anywhere deployment on the suite. | Run the Mobile readiness checks and keep Anywhere as the source system. | Licensing in Maximo Application Suite 9.2 |
| An inventory of Anywhere applications | You can only move what you have listed. | Mandatory | The Anywhere administration on the source system. | A list of applications, custom fields, actions and integrations. | The list has an owner and a task count. | Technicians are moved with unnamed custom buttons left behind. | Finish the inventory for the first role before cutover. | Modules and applications in Maximo Application Suite 9.2 |
| Manage data on the target for that task | Mobile shows Manage records. | Mandatory | Work, asset, location, labor and assignment on the MAS workspace. | The work order the Anywhere user would have opened, now present in Manage. | Find it in Manage and on the device. | The device is empty because the records are only in the old environment. | Load or replicate the records the task needs. | Modules and applications in Maximo Application Suite 9.2 |
| A field-by-field gap for the first task | Custom Anywhere fields are not on the Mobile screen until you put them there. | Mandatory | The inventory beside the Mobile screen for that task. | Each field marked as present, configured, or still a gap. | Complete the task and compare the saved fields with the inventory. | A required old field is silently dropped. | Configure it or change the task before cutover. | Modules and applications in Maximo Application Suite 9.2 |
| One online save read back in Manage | The replacement has to persist. | Mandatory | Mobile and Work Order Tracking, as in the Mobile course. | One update saved from the device and visible on the work order. | A second person reads it in Manage. | The device shows success and Manage does not change. | Fix the online path before retiring the Anywhere screen. | Modules and applications in Maximo Application Suite 9.2 |
| Offline only for tasks that work offline today | Offline is a behaviour you re-test, not a flag you copy. | Conditional | The Mobile offline configuration and the inventory’s offline column. | One task the technicians already do offline, retested after reconnect. | Update offline, reconnect, and read the work order back. | Anywhere offline is assumed to be identical. | Retest that task. Leave other tasks online. | Modules and applications in Maximo Application Suite 9.2 |
A. Ready to configure
- The Mobile tier and client are ready, using the Mobile course’s checklist A.
- The Anywhere inventory exists for the first role.
- The target site has the records that role updates.
- One task is chosen.
B. Ready for the first end-to-end journey
- The technician completes that task on Mobile.
- Manage shows the same business result.
- Every field the task requires is either saved or still listed as a gap.
- The Anywhere screen for that task is still available until you accept the result.
C. Ready for production operation
- Each role has a finished inventory and an accepted Mobile path.
- Device build, TLS and lost-device handling match the Mobile production list.
- Custom integrations from Anywhere have an owner on the new path.
- The old client is retired only for tasks whose result has been read back in Manage.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
Transition-only lesson. Anywhere is not presented as available on MAS 9.x. Maximo learning content starts at 7.6.1.3.
- An inventory of the existing Anywhere applications and a target Mobile training environment.
- Representative technician tasks and expected offline behavior.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
IBM states that Anywhere is available only through MAS 8.8 and is not available in MAS 8.9. This lesson is a transition assessment, not an Anywhere installation guide for current MAS.
Moving a mobile process involves forms, data selection, offline behavior and synchronization, not only replacing the client application.
Topics in this series
- Current field-process inventory
- Target capability mapping
- Configuration changes
- Online/offline parity
- Rollout and reconciliation
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- List the existing screens, custom fields, actions, scripts and integration dependencies.
- For each task, identify the supported target Mobile capability or a documented gap.
- Prepare a target test record with the required reference data.
- Execute the same business task online and offline in the target client.
- Compare server results, errors and recovery with the requirement before accepting parity.
03 · Practical example
Fictional teaching example
A fictional technician needs inspection answers, a material issue and a photo before completing work. All three outcomes must be verified; a similar-looking target form is insufficient.
04 · Practice and verify
Build a task-by-task transition matrix with target route, configuration, observed result and unresolved gap.
Expected result
Every required field task has demonstrated target behavior or a clearly recorded gap and owner.
Common mistakes
- Assuming old mobile customizations transfer unchanged.
- Publishing Anywhere as a current MAS add-on.
05 · Advanced concepts
Plan device rollout, pending transaction handling and rollback/recovery for the field process. Reconcile all queued work before retiring a client.
IBM references
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench