Forgot your password?
New user?
Delays in LADPW Upgrade from 4.1 to 6.2
Up to MAXIMO 6.x Upgrade
- We have a very large database. 2.5 million work orders and 1.2 million assets in addition to a commensurate volume of job plans, PMs, labor, tools, items, etc...
- Initially, the plan was to use the upgrade scripts provided by MRO, but, after attempting this approach for a few weeks, our IBM consultant saw that it was very time consuming, prone to failures, and, even if it ran successfully, would not result in a timely, 3-4 day, upgrade process. This was the initial delay in our upgrade project.
- The strategy was changed to use a data migration approach instead, where our consultant would develop a script to convert each table from the 4.1 structure to the 6.2 structure one at a time. Each time a script is developed to convert a table successfully, that script is added to a procedure with the rest of the scripts until, eventually, the entire 4.1 database can be converted to 6.2 by running this one procedure that contains all of the individual scripts. The migration strategy was implemented in November of 2007. As of today's date (6-5-08) we do not yet have a complete migrated data set. The time needed to develop these scripts and test the resulting data conversion is the primary source of delay in our upgrade project.
- Our IBM data migration consultant also had some family medical issues come up during our upgrade and was, understandably, not focused on our project for several weeks. IBM is talking about getting another database consultant to focus on the hands-on data conversion activity while keeping the original consultant to oversee the process and ensure consistant strategy.
- We experienced some additional delay in getting a change request for application extensions and crossover domains finalized and submitted for approval to our CIO. The application extensions and crossover domains are being implemented to replace existing functionality in Maximo that we created using triggers in 4.1. IBM does not support the use of triggers with Maximo.
- Now that the change request for the application extensions and crossovers has been approved, I anticipate that there may be a week or two delay in getting an IBM resource assigned to this task and started on it.
- Since we do not have a complete data set with our custom internal functionality, we are unable to fully test our upgraded maximo or invite our users into it to try it out, evaluate our "What's New" training material, and show us any other issues that should be corrected or modified prior to our expected roll-out in September of 2008.
Powered by
Ploneboard
SCMUG Meeting - April 23, 2008
