When I moved to India about two years ago, I arrived with my own expectations regarding emerging markets. One of them was that the lack of legacy IT applications and infrastructure would make these markets an ideal place for new technologies and delivery models like as-a-service to thrive. In other words, organizations in emerging markets would “leapfrog” to new technologies without going through some of the prior technology investments witnessed in developed markets. Unfortunately, the reality is not that simple.
One of the key takeaways of my recent reports (Australia, China, India Set The Pace For Asian IT Services and The Changing Face Of ASEAN IT Services — to be published in January 2012) is that most of the growth in emerging countries will come from traditional IT services such as ERP implementation, infrastructure deployment, and system integration. Against common belief, emerging services — including cloud and mobility — will represent less than 20% the total annual growth in emerging markets in 2015.
I see several reasons for this:
Lack of governance and planning. An IT department’s role is merely one of provider of applications and infrastructure, whose main objective is to react to business needs.
Lack of internal skills. Client organizations do not have the adequate skills internally to take on complex transformational projects involving new technologies such as virtualization, business analytics, and mobile enterprise application integration platforms.
Lack of IT services culture. Most client organizations in emerging markets leverage external skills to help them with basic tasks such as hardware maintenance and software deployment.
A few days ago, CSC announced its new Celeriti banking platform, which consists of five products: Celeriti Customer, Celeriti Deposits, Celeriti Loans, Celeriti Cards, and Celeriti Merchant. The solution includes, for example, a strong business process focus, business intelligence, and the so-called Web Portal User Interface. The platform has been built around IBM application infrastructure, runs on multiple operating systems such as z/OS, z/Linux, Linux, and Windows, and has been validated for use with the IBM Banking Industry framework. Here is my initial reaction to Celeriti.
So you need to formulate an application modernization decision -- what to do with a given application -- how do you begin that decision making process? In the past, modernization decisions were often simply declared -- "We are moving to this technology" -- for a number of reasons, such as, it:
Keeps us current on technology.
Provides a more acceptable user-interface or integration capability.
Increases our exposure to access by external customers.
Increases the volume of business transaction we can process.
Trades custom/bespoke applications for standardized application packages such as ERP, payroll, human resources, etc.
Fast-forward to today -- you could simply go with your gut -- declare a solution based on what you currently know (or think you know) about the application in question. But it's a new day baby -- a proposal like that, without proper justification, is likely to be met with one of two responses from management: