IBM MAXIMO SG24-7645-00 - Manual (Page 39)

Chapter 3. Project Planning 25
Draft Document for Review May 23, 2008 10:14 am 7645ProjPlan.fm
• Concurrent users
• Transaction processing time with database and external data sources
Go-Live
– Plan cut-over strategy
– Migration to production environment
– Execute each of the above test cases introduction environment to ensure
zero-performance glitch in the live environment
– Training needs to be provided to all or some of the users. Recommended
approach is ‘Train-the-Trainer’. Training to 3 types of users:
• End Users: Functional training to the user community on how to use
various functional aspects of the software. This can be done with
focussed groups or general groups depending on how the client
organization is structured
• Role Based Training: This training is specific to certain groups. Support
Purchase Administrator, Supervisor and so on, on how they can
approve or disapprove certain tasks, manage their queue and so on
• Administrative Training: Once the implementation team walks out, there
has to be an internal designated person to manage the system. This
person will be responsible for system availability, creation of new
reports, enhancements, adding users, roles security groups and so on.
Phase 5: Support
Key Roles: Project Manager, Maximo Developers
Optional Roles: Business Analyst, Solution Architect
Key Activities:
Some organizations do not have strong IT presence and opt for the
implementation team to provide continued system support. The basic tasks the
support team has to perform are, but are not limited to:
– Manage system availability
– Make enhancements to accommodate evolving business processes
– Create and deploy new reports
– Build new integrations
– Capacity planning for additional users and or organizations
The above five phase methodology is generic but includes most of the basic
activities that need to be considered and planned for in an implementation.
However, what the section does not include is how and what is the customer’s