Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 6

Cisco Systems, Inc.

: Implementing ERP
Group 11, Section B
Abhinav Kumar Aniruddha Dobre Avik Sinha Kannuri Gowtam 2011PGP505 2011PGP546 2011FPM03 2011PGP679

Riya Ghosal
Rupsa Chakravarty Subrata Mondal

2011PGP827
2011PGP837 2011PGP898

IT Model (before January, 1994)


Specifications: o Unix based software package Legacy system o Functions supported Financial, Manufacturing, Order Entry o Highly customized o Standardization o Shared architecture Weakness: o Lower degree of redundancy, reliability, maintainability and scalability o Dependency on a single vendor largest single customer o Reactive approach band aid after the problem is sought o Independence of modules less or no integration

ERP Solution (Yes / No)


Why to avoid? o Independence of the functional areas o Reliance on Legacy system continuance of band aiding How to convince? o Failure of Legacy system band aid failed o Corruption of central database company shut down for 2 days o Urgent need for replacement o Urgent need for integration no separate decisions by functional areas o Shortage of time no phased implementation o No customization

ERP Solution Resistance


Resistances of implementation: o Fear of getting the project out-of-control o Fear of getting substandard results o No formal business case o No economic justification of $15 million investment o Uncertain duration of the project (5 months or 15 months) Resistances of leadership: o Highest capital project ever in the company o Failure may lead to end of career

Big Bang The Shades


Advantages: o Implementation was backed by the best minds of company o Implementation in 5 Tracks and 4 CRPs Gap analysis, Integration, Modification and Incremental development o Data Warehouse single source of data / bridge between past and future Disadvantages: o Hardware capability o Inadequate testing with partial database

Performance Evaluation
Lucky enough?

The implementation planning schedule doesnt say so


o Thorough business knowledge was allowed to flow RIP

implementation o Incremental development reduction of risk o Data Warehouse one-stop solution for information needs o Hardware purchase based on promised capability transfer of risk

Why dip in performance? o Oracles first release of ERP product lack of experience o Shortage of time during implementation o Hardware architecture and size

You might also like