Billing and OSS World
Search
Weekly E-mail Newsletter 

Prone to Failure: Why CRM and Billing Systems Implementations Are High Risk

Dr. Raul Katz, Adjunct Professor in the Division of Finance and Economics at Columbia Business School, Presents Findings from Research on Why Certain Telecom Implementations Are Doomed from the Start

Dr. Raul L. Katz
08/26/2008
Continued from page 2

The North American wireless carrier tackled the replacement of a legacy CRM application with a Siebel solution in order to support marketing analysis and channel activities. After approximately two years of implementation work, the project was canceled and the carrier continued relying on the legacy application.

The satellite content distribution company decided to replace a legacy CRM application with Siebel. The project was expected to last 1.5 years but ended up requiring three years. However, once the application partially was implemented, a combination of factors (management changes in the company, higher than usual software license fees, and potential scalability problems) led to the cancellation of the project and consequent decommissioning of the project.

Figure 1 presents the schedule and budget outcome of the five cases:

Company                            Original Budget         Actual Budget       Final Outcome
                                    

Time
(Years)  

Cost
($M)          

 Time    

Cost
($M)      
  (*)

                                                                        

Wireless
Carrier
(North America)              

1.0        
$25            
2.0        

$80
(220%)  

Decommissioned
Satellite
Distribution
(North America)
1.5$153.0

$50
(133%)

Decommissioned
Wireless
Carrier
(Asia/Pacific)
2.3$2004.5

$450
(125%)

Implemented
Wireline
Carrier (Europe)
1.5$1352.2$195
(44%)
Implemented
Wireless/
Wireline
Carrier
(Latin America)
1.0N/A2.5N/AImplemented in wireless; canceled in wireline
*Percentage indicates budget overrun.

As the figure shows, the projects that led to a final cutover incurred cost overruns ranging between 44 percent and 125 percent and schedule extensions of seven months to two years. On the other hand, cancellations were decided after a timeline extension of more than a year, and a cost overrun exceeding 133 percent. What was the business impact of all these problems?

Impact on the Business

In addition to the economic losses, the impact of cancellations and delays varied by project. They can be categorized into two areas: technical and business impact. The technical impact (e.g. downtime, problems with data integrity) can be directly linked to the project itself. The business impact pertains more to the hypothetical inference of cause-effect from the delay or the cancellation of the project and business performance.

The technical impact can be easily ascertained in the case of projects that were completed.

Pages: Previous 1 2 3 4 5 6 7 8 9 Next


Share this article: Email, Slashdot, Digg, Del.icio.us, Yahoo!MyWeb, Windows Live Favorites, Furl
RSS Add this article feed to: RSS, My Yahoo, Newsgator, Bloglines

Read Comments [4]

Post a Comment

Email Email this article Comment Add a comment
Print Printer version Reprints Order reprints
RSS RSS Feed Bookmark Bookmark article







Subscribe to Billing & OSS World Magazine
First Name Last Name
E-mail

Sponsored LinksB/OSS Magazine Announcements