Do you mind sharing what the product is you're looking to remove? Most people don't realize that Linear, Calibration, & Scheduler are embedded into the core Maximo application and your install of those products is essentially just installing a license key to expose the functionality. In that scenario, you only need to create a new install without those add-ons and wouldn't do anything with the database. This scenario goes away with MAS because in that version these 3 apps are available in all systems at no additional charge.
You mentioned industry solution so I don't think you're in the "easy" situation. But even then, our industry solutions vary in complexity. Aviation and Civil Infrastructure are really multiple industry solutions combined. For example, Aviation has HS&E, Transportation, ACM, Service Provider, etc. in addition to Aviation specific functionality. Control Desk is an IT solution and is unique in that unlike all the other industry solutions which utilized a standard prefix (PLUSP for Service Provider for example), they took over the core tables, applications, etc. with no prefix. This makes it much more difficult to identify what will be impacted.
I've in the past built DBC files for removal of some of the smaller add-ons (Spatial, Anywhere, Maximo Mobile, etc.). That allowed us to remove the references of the product without having to migrate all of the data into a new system which would have been a significant outage. We had to build a new install, run the DBC file, and deploy new EAR files.
For larger products, it's difficult to say what the best approach would be. Reimplementing Maximo without the add-on helps ensure you avoid any remnants but can be an expensive endeavor for an organization with a lot of data. And depending on the approach, could result in significant downtime. The reimplementation would give you an opportunity to address issues with the initial implementation that can't be fixed in a running system, such as too many or not enough sites. Sometimes a reimplementation provides more business value than the cost but if the only change is removal of the industry solution, that becomes tough.
If this customer has another industry solution (Transportation & Oil and Gas for example) and plans to keep one of them long term, you may be better off sticking with both. With the MAS licensing, once you have an industry solution you pay the same price per user if you have 1 or more industry solutions.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 06-15-2022 13:06
From: Eric Godel
Subject: Remove Industry Soution
I would like to know if anyone has removed an industry solution from a production Maximo environment. Taking into consideration that any current data used in the solution specific tables or fields are not needed to be retained, or are easily moved to a new custom field. The solution has been installed for years, but there has never been any real use of the solution specific apps, or the solution specific functionality.
I know IBM does not support the removal of an industry solution, so the process would be rebuilding a new Maximo environment and preforming a database refresh into that new environment after its been custom modified.
Has anyone ever been successful in this task and what is the level of effort needed to pull this off without any long term problems?
Thanks so much for whatever information I can get!
#HSE/OilandGas
#Linear
#Nuclear
#Scheduling
#Spatial
#Transportation
#Utilities
------------------------------
Eric Godel
------------------------------