Symantec Erp Turmoil

23
SYMANTEC'S ERP TURMOIL

description

Case of Symantec Erp Turmoil and its Answer

Transcript of Symantec Erp Turmoil

Page 1: Symantec Erp Turmoil

SYMANTEC'S ERP TURMOIL

Page 2: Symantec Erp Turmoil

SYMANTEC

A leading software vendor specialized in Security and Information Management

Well known for Norton brand of security products

Operates in more than 40 countries and consist over 17500 employees. In 2005, the company made its largest acquisition to date, acquiring Veritas Software for approx. $13.5 billion

Page 3: Symantec Erp Turmoil

Use of Common Software

After acquisition, it began an ERP rollout known as Project Oasis. Its goal was to create a single ERP (Enterprise Resource Planning) system

Both companies were using Oracle E-Business suit 11d prior to the merger. Which seemed a good thing for SYMANTEC’s business operation

Page 4: Symantec Erp Turmoil

Requirement & Benefits

Combined company’s enterprise system was needed to combine Symantec and Veritas data from key business processes

A common enterprise system would also reduce the cost of maintaining Symantec’s IT infrastructure and licensing fees for the enterprise software.

Page 5: Symantec Erp Turmoil

Steps Taken by Symantec

Company opted to upgrade to oracle’s E-Business suite on Sun Solaris Server

They used oracle fusion middleware portal on the front end ,providing a single point for all of partners and customers

Page 6: Symantec Erp Turmoil

Problem with New System

The initial reaction of launching the new system was unquestionably negative

Users were unhappy with this new system Customers began calling Symantec’s

support team for solution in record numbers ,but the company was unprepared to meet the increased demand for customer support

Waiting time ballooned from an average of 2 min. to an average of 25 min. for a call

Page 7: Symantec Erp Turmoil

Problem Continued

Once customer reached a Symantec employee they had to spend 20 more min. troubleshooting the problems and they were often told that there was nothing that could be done

Customers were also unhappy with Symantec’s changes to its stock-keeping unit product system

Page 8: Symantec Erp Turmoil

Decision Backfired

Symantec tried to improve the systems by single set of codes, But-

Some small distributors and partners didn’t update their system to handle new SKU (Stock Keeping Unit) system

Extended the date but the overhaul still represented an annoyance for many customers

Changes to software licensing were another irritating thing to customer

Kept couple of weeks in getting license Not coordinated with rest of the project ‘OASIS’ Difficulty in buying Symantec’s products via

companies like Ingram Micro Partners were unhappy with time consuming processes

Page 9: Symantec Erp Turmoil

Result of Missteps

Symantec was in danger to loose many loyal customers

Company’s shortsightedness in implementing project ‘OASIS’

Earnings were less than expected Needed to cut $200 million in annual

costs Top management had to confess their

mistakes

Page 10: Symantec Erp Turmoil

Project Nero

For the purpose of undoing mistakes, the company immediately came up with Project Nero. The goal was to recapture the loyalty of customers who got annoyed after OASIS. This was planned to done by-

Reaching to those customers Fixing the problems with their information

systems to improve response time and streamline operations

Page 11: Symantec Erp Turmoil

Implementation

Company added 150 customer representatives to handle increased volumes of calls reduce wait times increase customer satisfaction Company’s executives travelled the country

for improving relations with angered customers and partners

Symantec also used Net promoter technology to measure and increase customer loyalty

Page 12: Symantec Erp Turmoil

Result

Symantec’s customer satisfaction levels which were extremely low after OASIS, improved after Nero project

Symantec reported that it now enjoys satisfaction level at par with the rest of the industry and averted a potential danger, though they never revealed the result of net promoters survey and their total damage

Page 13: Symantec Erp Turmoil

Questions

Page 14: Symantec Erp Turmoil

Q1. What concepts in this chapter are illustrated in this case?

Page 15: Symantec Erp Turmoil

Q2. What Management, Organization, and Technology factors were responsible for Symantec’s difficulties in overhauling its ERP systems?

Page 16: Symantec Erp Turmoil
Page 17: Symantec Erp Turmoil
Page 18: Symantec Erp Turmoil
Page 19: Symantec Erp Turmoil

Q3. Was Symantec’s response to the problem adequate? Explain your reasoning

Page 20: Symantec Erp Turmoil

Q4. What would you have done differently to prevent the implementation problems that arose at Symantec?

Page 21: Symantec Erp Turmoil

Q5. If you were a partner or customer of Symantec, would you have switched vendors in response to the ERP overhaul issues? Why or why not?

Page 22: Symantec Erp Turmoil

Conclusion

Symantec’s ERP Turmoil shows that even the most careful planning and well designed system can quickly go down if customers are unable to understand or use the information system properly

Page 23: Symantec Erp Turmoil

Thanks For Your Time