1. ERP IMPLEMENTATION LIFE CYCLE
1.1. SELECTION OF PACKAGES
1.2. PROJECT PLANNING
1.3. ANALYSIS GAP
1.4. RE - ENGINEERING
1.5. TRAINING
1.6. APPLICATION
1.7. MAINTENANCE
2. EIS COMPONENT
2.1. HUMAN RESOURCE ( HR )
2.2. SUPPLY CHAIN MANAGEMENT ( SCM )
2.3. INVENTORY
2.4. SALES
2.5. PURCHASE
2.6. FINANCE & ACCOUNTING
2.7. CUSTOMER RELATIONSHIP MANAGEMENT ( CRM )
2.8. ENGINEERING / PRODUCTION
3. IMPACT OF EIS PROJECTS
3.1. SEEN
3.1.1. INITIAL SOFTWARE COST
3.1.2. INITIAL HARDWARE COST
3.2. UNSEEN
3.2.1. DUAL SYSTEM REQUIREMENT
3.2.2. ANNUAL SUPPORT FEES
3.2.3. DATA MIGRATION
3.2.4. SOFTWARE DE-BUGGING AND PATCH APPLICATION
3.2.5. SOFTWARE UPGRADES
3.2.6. NETWORK ARCHITECTURE UPGRADES
3.2.7. IT STAFF INCREASE
3.2.8. BUSINESS DISRUPTION
3.2.9. BUSINESS PROCESS RE-DEFINITION
3.2.10. PROCESS MANAGEMENT
3.2.11. CONSULTING FEES
3.2.12. TRAINING
3.2.13. SOFTWARE CUSTOMIZATIONS
3.2.14. SOFTWARE INTEGRATION
3.2.15. IMPLEMENTATION TEAMS TURNOVER
4. IMPLEMENTATION GUIDELINES
4.1. UNDERSTAND CORPORATE NEED AND CULTURE
4.2. COMPLETE BUSINESS PROCESS CHANGE
4.3. PROVIDE STRONG LEADERSHIP
4.4. CHOOSE A BALANCED TEAM
4.5. SELECT A GOOD IMPLEMENTATION METHODOLOGY
4.6. TRAIN EVERY ONE
4.7. COMMITMENT TO ADAPT AND CHANGE
5. IMPLEMENTATION STRATEGIES
5.1. PILOT IMPLEMENTATION
5.1.1. EXPLANATION
5.1.1.1. THE NEW SYSTEM REPLACES THE OLD ONE IN SMALL SCALE THROUGH LOCATION BY LOCATION
5.1.2. ADVANTAGES
5.1.2.1. EASY TO CONTROL
5.1.2.2. EASY TO EVALUATE , OLD AND NEW SYSTEM BOTH RUNNING TOGETHER
5.1.2.3. LOW RISK
5.1.2.4. EASY TO TRAIN STAFF
5.1.3. DISADVANTAGES
5.1.3.1. IT CAN BE SLOW TO GET PILOT TO COMPLETELY REPLACE THE OLD SYSTEM
5.1.3.2. A PILOT MAY NOT SHOW UP A PROBLEM THAT A FULL SCALE IMPLEMENTATION WOULD
5.2. BIG-BANG ( DIRECT ) IMPLEMENTATION
5.2.1. EXPLANATION
5.2.1.1. COMPLETELY REPLACING OLD SYSTEM WITH THE NEW ONE IN ONE GO
5.2.2. ADVANTAGES
5.2.2.1. THE MOST RAPID OF ALL STRATEGIES
5.2.2.2. LOW RISK OF CONFUSION BETWEEN OLD AND NEW SYSTEMS
5.2.3. DISADVANTAGES
5.2.3.1. MOST STRESSFUL FOR THE USERS
5.2.3.2. MOST DIFFICULT TO TRAIN STAFF
5.2.3.3. MOST STRESSFUL FOR THE DEVELOPERS
5.2.3.4. MOST RISKY
5.3. PHASED IMPLEMENTATION
5.3.1. EXPLANATION
5.3.1.1. THE NEW SYSTEM IS BROUGHT IN STAGES ( PHASED )
5.3.2. ADVANTAGES
5.3.2.1. VERY STRUCTURED
5.3.2.2. LOWER RISK
5.3.2.3. EASY TO TRAIN STAFF
5.3.3. DISADVANTAGES
5.3.3.1. SLOWER THAN DIRECT IMPLEMENTATION
5.3.3.2. A PHASED IS NEED TO BE COMPLETED TO GET THROUGH THE NEXT PHASED
5.4. PARALLEL IMPLEMENTATION
5.4.1. EXPLANATION
5.4.1.1. BOTH SYSTEM ARE OPERATE INDEPENDENTLY , IF ALL GOES WELL , THE OLD SYSTEM STOPPED
5.4.2. ADVANTAGES
5.4.2.1. THE OLD SYSTEM CAN STILL BE USED IF ANY INITIAL PROBLEMS
5.4.2.2. EASY TO TRAIN STAFF
5.4.2.3. EASY TO EVALUATE
5.4.2.4. BOTH SYSTEM CAN EASILY BE COMPARED
5.4.3. DISADVANTAGES
5.4.3.1. EXPENSIVE
5.4.3.2. SOME RISK - GREATER CHANCE OF CONFUSION IF TWO DIFFERENT ERROR ARE BEING RUN SIDE BY SIDE
6. IMPLEMENTATION METHODOLOGIES
6.1. VANILLA IMPLEMENTATION APPROACH
6.1.1. MINIMAL CUSTOMIZATION OF EIS PACKAGES
6.2. CUSTOMIZATION
6.2.1. THE VENDOR SOFTWARE IS MODIFIED TO FIT THE PRACTICES OF THE USER ORGANIZATIONS
7. ALTERNATIVE EIS DEVELOPMENT METHODS
7.1. DEVELOP IN HOUSE
7.1.1. ADVANTAGES
7.1.1.1. BEST FIT WITH ORGANIZATIONAL NEEDS
7.1.2. DISADVANTAGES
7.1.2.1. MOST DIFFICULT TO DEVELOP
7.1.2.2. MOST EXPENSIVE
7.1.2.3. SLOWEST
7.2. IN HOUSE DEVELOPMENT WITH VENDOR SUPPLEMENTS
7.2.1. ADVANTAGES
7.2.1.1. GAIN COMMERCIAL ADVANTAGES COMBINED WITH ORGANIZATIONAL FIT
7.2.2. DISADVANTAGES
7.2.2.1. DIFFICULT TO DEVELOP
7.2.2.2. EXPENSIVE
7.2.2.3. SLOW
7.3. BEST OF BREED
7.3.1. ADVANTAGES
7.3.1.1. THEORETICALLY GAIN BEST OF ALL SYSTEMS
7.3.2. DISADVANTAGES
7.3.2.1. DIFFICULT TO LINK MODULES
7.3.2.2. SLOW
7.3.2.3. POTENTIALLY INEFFICIENT
7.4. CUSTOMIZED VENDOR SYSTEM
7.4.1. ADVANTAGES
7.4.1.1. RETAIN FLEXIBILITY WHILE KEEPING VENDOR EXPERTISE
7.4.2. DISADVANTAGES
7.4.2.1. SLOWER
7.4.2.2. USUALLY MORE EXPENSIVE
7.5. SELECTED VENDOR MODULES
7.5.1. ADVANTAGES
7.5.1.1. LESS RISK
7.5.1.2. RELATIVELY FAST
7.5.1.3. LEAST EXPENSIVE
7.5.2. DISADVANTAGES
7.5.2.1. IF EXPAND , LONG RUN TIME AND HIGHER COST
7.6. FULL VENDOR SYSTEM
7.6.1. ADVANTAGES
7.6.1.1. FAST
7.6.1.2. LESS EXPENSIVE
7.6.1.3. EFFICIENT
7.6.2. DISADVANTAGES
7.6.2.1. INFLEXIBLE
7.7. APPLICATION SERVICE PROVIDER
7.7.1. ADVANTAGES
7.7.1.1. LEAST RISK
7.7.1.2. LEAST COST
7.7.1.3. FASTEST
7.7.1.4. LEAST SUBJECT TO VENDOR CHANGE
7.7.2. DISADVANTAGES
7.7.2.1. AT THE MERCY OF ASP
7.7.2.2. NO CONTROL
7.7.2.3. SUBJECT TO PRICE INCREASE
8. MANAGING RISK ON EIS PROJECTS
8.1. RISK IS POTENTIAL FAILURE POINT
8.2. THERE ARE THOUSANDS/MILLIONS OF POTENTIAL FAILURE POINTS ON EIS PROJECT
8.3. 5 STEPS ON MANAGING RISK
8.3.1. FIND POTENTIAL FAILURE POINTS OR RISK
8.3.2. ANALYZE THE POTENTIAL FAILURE POINTS TO DETERMINE THE DAMAGE THEY MIGHT DO
8.3.3. ASSESS THE PROBABILITY OF FAILURE OCCURING
8.3.4. BASED ON THE FIRST THREE FACTORS , PRIORITIZE THE RISK
8.3.5. MITIGATE THE RISK THROUGH WHATEVER ACTION IS NECESSARY