what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

One other thing to check is if other .jsp, .xml, etc files were changed/customized and update them according to the new version. For example, if some logic was built in a .jsp file, that logic will need to be checked/added in MAS 9 as well.

------------------------------
Liliana Malaescu
Naviam (formerly known as ZNAPZ)
Senior Maximo Technical Consultant
Romania
------------------------------

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

Hello

so i need to check whether the files contain any embedded logic or UI modifications.

If they do, these customizations must be reviewed and updated to ensure compatibility with MAS 9 ?

------------------------------
Khairi Chmengui
------------------------------

Original Message:
Sent: Mon November 03, 2025 04:55 AM
From: Liliana Malaescu
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

One other thing to check is if other .jsp, .xml, etc files were changed/customized and update them according to the new version. For example, if some logic was built in a .jsp file, that logic will need to be checked/added in MAS 9 as well.

------------------------------
Liliana Malaescu
Naviam (formerly known as ZNAPZ)
Senior Maximo Technical Consultant
Romania

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

That is correct.

------------------------------
Liliana Malaescu
Naviam (formerly known as ZNAPZ)
Senior Maximo Technical Consultant
Romania
------------------------------

Original Message:
Sent: Tue November 04, 2025 02:38 AM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

Hello

so i need to check whether the files contain any embedded logic or UI modifications.

If they do, these customizations must be reviewed and updated to ensure compatibility with MAS 9 ?

------------------------------
Khairi Chmengui

Original Message:
Sent: Mon November 03, 2025 04:55 AM
From: Liliana Malaescu
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

One other thing to check is if other .jsp, .xml, etc files were changed/customized and update them according to the new version. For example, if some logic was built in a .jsp file, that logic will need to be checked/added in MAS 9 as well.

------------------------------
Liliana Malaescu
Naviam (formerly known as ZNAPZ)
Senior Maximo Technical Consultant
Romania

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

We went live in September. A couple areas that we struggled with:

• User management - users are now stored in a Mongo db in the Suite level and synced with your other applications (like Manage). That wouldn't have been a difficult change except that we have custom Person record IDs. We needed to develop a somewhat complicated workout to the standard user creation process.
• Spatial - in general, it took us a very long time to set up and then test Spatial (which integrates with ArcGIS for us). We hit multiple show-stopping bugs that required some development from IBM. Expect to spend a while testing this if you use it.

Finally, I'd recommend doing an assessment of your users to determine which would be appropriate to have authorized vs. concurrent access in the new App Point license structure. It can save you a lot of points to give your users the right license for them. For example, our users are almost all concurrent, but we have roughly 10% of our heaviest users on authorized.

------------------------------
Carl Nelson
------------------------------

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

Hello
thank you I'll keep that in mind. If you don't mind, could you please share the link so we can review it as well?

Regards

------------------------------
Khairi Chmengui
------------------------------

Original Message:
Sent: Mon November 03, 2025 08:43 AM
From: Carl Nelson
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

We went live in September. A couple areas that we struggled with:

• User management - users are now stored in a Mongo db in the Suite level and synced with your other applications (like Manage). That wouldn't have been a difficult change except that we have custom Person record IDs. We needed to develop a somewhat complicated workout to the standard user creation process.
• Spatial - in general, it took us a very long time to set up and then test Spatial (which integrates with ArcGIS for us). We hit multiple show-stopping bugs that required some development from IBM. Expect to spend a while testing this if you use it.

Finally, I'd recommend doing an assessment of your users to determine which would be appropriate to have authorized vs. concurrent access in the new App Point license structure. It can save you a lot of points to give your users the right license for them. For example, our users are almost all concurrent, but we have roughly 10% of our heaviest users on authorized.

------------------------------
Carl Nelson

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

I assume you mean a link for the AppPoint assessment. It was nothing formal. All of our non-admin users were concurrent by default. I downloaded login tracking from Users -> Manage Sessions and looked for users that were logged in the most (and ones logged in in the morning, our heaviest traffic time). We then made those users authorized. Since they were all Premium users, that brought their points from 15 to 5. That ended up cutting about 100 points for us, based on data I looked at after go-live.

------------------------------
Carl Nelson
------------------------------

Original Message:
Sent: Tue November 04, 2025 02:43 AM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

Hello
thank you I'll keep that in mind. If you don't mind, could you please share the link so we can review it as well?

Regards

------------------------------
Khairi Chmengui

Original Message:
Sent: Mon November 03, 2025 08:43 AM
From: Carl Nelson
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

We went live in September. A couple areas that we struggled with:

• User management - users are now stored in a Mongo db in the Suite level and synced with your other applications (like Manage). That wouldn't have been a difficult change except that we have custom Person record IDs. We needed to develop a somewhat complicated workout to the standard user creation process.
• Spatial - in general, it took us a very long time to set up and then test Spatial (which integrates with ArcGIS for us). We hit multiple show-stopping bugs that required some development from IBM. Expect to spend a while testing this if you use it.

Finally, I'd recommend doing an assessment of your users to determine which would be appropriate to have authorized vs. concurrent access in the new App Point license structure. It can save you a lot of points to give your users the right license for them. For example, our users are almost all concurrent, but we have roughly 10% of our heaviest users on authorized.

------------------------------
Carl Nelson

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

Suggest:

1. Ensure the underlying RHOS environment is configured according to IBM documentation to support MAS. (Compute, networking, security, etc.)
2. Any current interfaces to/from Maximo and well documented and function according to those documents. If they are not using REST API, perhaps an opportunity to re-work them to do so, but at least you have documentation for testing during/after the upgrade.
3. Consider archiving historical data and only moving more recent data into the new MAS environment.

Hope these help.

------------------------------
John Q. Todd
Sr. Business Consultant
Total Resource Management
------------------------------

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

Hello

Thank you for the detailed recommendations ,these are very helpful. 

I'll make sure to review the RHOS configuration and verify our current interfaces and data migration approach accordingly.

Regards

------------------------------
Khairi Chmengui
------------------------------

Original Message:
Sent: Mon November 03, 2025 10:49 AM
From: John Q. Todd
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

Suggest:

1. Ensure the underlying RHOS environment is configured according to IBM documentation to support MAS. (Compute, networking, security, etc.)
2. Any current interfaces to/from Maximo and well documented and function according to those documents. If they are not using REST API, perhaps an opportunity to re-work them to do so, but at least you have documentation for testing during/after the upgrade.
3. Consider archiving historical data and only moving more recent data into the new MAS environment.

Hope these help.

------------------------------
John Q. Todd
Sr. Business Consultant
Total Resource Management

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

When it comes to RHOS, if you are install on Baremetal or Virtualized version of SNO, it comes down to the foundation. 

RHOS as a base will install on the assigned disk from the RHOS install page. However during the CLI installation you need have assigned a 2nd disk for Persistence Volume Storage (PVC).

RHOS won't partition the disk for PVC for you. You will need to assign at least 20-24 cores before installation and assigned at least 125 GB of ram. 

With Baremetal this is an issue if you have installed RHOS already and have a single raid configuration. You will need to delete that raid configuration and start over and have 2 sets of raids being one of disks for base install and 2nd for PVC. For virtual, you will be in the same boat, setup your VM with primary disk set of static data for install, and add a 2nd drive for PVC. 

It comes down to a good project plan with such tasks:

Existing Custom Classes - convert them to Automation Scripts, if not possible can the business logic behind them change to work within an automation or workflow?

Custom Reports should work for the most part, user testing is key

Mobile (anywhere, everyplace) these will have to all be reimplemented within Maximo Mobile, if you are using a 3rd party Mobile confirm they support API. 

Integration and transmission methods (RMI is deprecated) There are ways to send data flat file to RHOS with SNO. 

Reach out to me if you have more questions Khairi. 

------------------------------
Roger Vallee
------------------------------

Original Message:
Sent: Tue November 04, 2025 02:45 AM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

Hello

Thank you for the detailed recommendations ,these are very helpful. 

I'll make sure to review the RHOS configuration and verify our current interfaces and data migration approach accordingly.

Regards

------------------------------
Khairi Chmengui

Original Message:
Sent: Mon November 03, 2025 10:49 AM
From: John Q. Todd
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

Suggest:

1. Ensure the underlying RHOS environment is configured according to IBM documentation to support MAS. (Compute, networking, security, etc.)
2. Any current interfaces to/from Maximo and well documented and function according to those documents. If they are not using REST API, perhaps an opportunity to re-work them to do so, but at least you have documentation for testing during/after the upgrade.
3. Consider archiving historical data and only moving more recent data into the new MAS environment.

Hope these help.

------------------------------
John Q. Todd
Sr. Business Consultant
Total Resource Management

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------

Hi Khairi,

Aside from refactoring/removing existing Java customizations, the main points to watch out for are:
• Infrastructure shift: MAS runs on OpenShift/Kubernetes. It's not a typical app server upgrade. Be sure the team is comfortable with containers, operators, PVCs, and cluster sizing. One common blocker is under-sizing the cluster.
• Database considerations: Validate compatibility and sizing early; especially if changing to Db2. Also check for collation, timezone configurations, and case sensitivity because these may break the migration in silence.
• Integration Layer Changes: Integration is handled differently - via App Connect/queues/OSLC. Any direct DB or legacy Maximo Integration Framework setups will need review.
• Security & Authentication: MAS uses IAM/SSO by default. Plan for federation - Azure AD / Keycloak / ADFS / etc. Review how service accounts & API keys will be handled.
• Report impacts BIRT / Cognos: Existing BIRT reports generally work, but scheduling, output paths, and libraries are different. Cognos integration also changes (new landing page, namespaces, etc.).
• UI / MAF / Work Centers: Some old UI behaviors don't exist anymore. If users rely heavily on classic toolbar customizations or Start Center tricks, they might need a redesign.
• Automation Scripts / Escalations / Workflows: Generally these migrate OK, but anything referencing custom classes or deprecated MBO events needs attention.
• Licensing and Entitlements: MAS utilizes consumption-based entitlements. Align the license model to real usage to avoid unexpected cost increases.

We still at your disposal to assist you in your migration project.

------------------------------
Nacef Sifi
Maximo Offering Manager / Maximo Consultant
VAGANET
0753122351
------------------------------

Original Message:
Sent: Fri October 31, 2025 07:05 PM
From: Khairi Chmengui
Subject: Maximo 7.6.1.2 -> MAS 9: What Should We Really Watch Out For?

what are the key considerations or pitfalls that teams should keep in mind when planning a migration from Maximo 7.6.1.2 to MAS 9 , aside from shifting or refactoring all the existing Java customizations?

------------------------------
Khairi Chmengui
------------------------------