1. Definition and Analysis
• Hold discussions with various functional personnel to establish the actual number of systems operating at client site, what they are used for, why and how often
• Produce the Project Scoping Document outlining current situation, proposed solution and budgeted time
Challenge : REQUISITE EXPERTISE - No two clients are the same Process
2. Design
• Prepare various functional reports - specifies current scenario and wish list
• Prepare Design document which specifies how the system is going to work
• Prepare test scripts to be followed on system testing
• Map out the interface paths to various modules
Challenge : INFORMATION SHARING - Availability of staff Process
3. Build
• Configure system as per set up document specifications i.e. transfer conceptual model into reality
• Test system to verify accuracy (preliminary tests)
Challenge : TECHNICAL ENVIRONMENT - System functionality Process
4. Transition
• Train users on their specific areas
• Assist in test data compilation and system testing by users
• Finalise the Live system and captured opening balances
Challenge : USER RESISTANCE Understanding and acceptance data preparation Process
5. Production
• Official hand holding
• Effectiveness assessment
• Business and Technical Direction recommendations
• Technology
• Technology is an enabler, not the driver (it is there to assist the organisation to achieve business goals)
• It is a means to an end, not the end
• Conclusion
• ERP systems provide a mechanism for implementing systems where a high degree of integration between applications is required
• The Business Case or Value Proposition for implementation must be outlined
• To successfully implement a proper mix of people, processes and technology should be maintained