Skip to main content

IT and the Communication Industry

After lecturing on SOA concepts, Architecture and Technology, I present Case Studies. While presenting Case Studies, I ask my students: "Why many Case Studies and Success Stories are from the Telco industry?" Usually they do not provide a good answer to the good question.

It is a good question because the answer is based upon Business dimension, Technology dimension and the relationship between the two dimensions. 

Why SOA implementation is necessary for Traditional Telco Service Companies?
For many years, Traditional Telco companies revenues were based upon telephone calls billing.
In USA Bell Labs was split to Baby Bells. In other countries these companies were Monopolies or Duopolies.  
Due to lack of competition, their revenues were high.

When Voice over IP matured they found a lot cheaper competition such as Skype

When someone traveled to other countries, he called his family in his home country. The Telco service providers earned money.

However, when I paid a visit to Bhutan two years ago, I could find free Internet services in almost every hotel or guest house. I used Skype. I could talk to my friends and relatives as much as I liked to. I paid nothing to a Telco Service provider
The Computer Camera enables another type of data classical phone calls were not able to provide: I could see my friends and relatives during our phone calls. 

Bhutan is just an example of Developing Country. You may be sure that me and anybody else could use free Skype calls from Developed Countries.

The traditional Telco Companies had to reinvent themselves or perish. 
They developed new Business Model based on new services e.g. Content Services, Internet Infrastructure Services etc. 

As Far as Information Technology is concerned, frequent and major changes were required in order to support the new Business model and the New Business Services. 

Agility or ease of Change is SOA's major Value Proposition. The Traditional Telco Services providers transformed their IT systems to Service Oriented Architecture based systems in order to support the IT Systems changes.  

SOA and Cellular Phone Service Companies
The emergence of Cellular Phones is another threat to the Traditional Telco model, which was not mentioned in the previous paragraph.

I would like to describe the beginning of my SOA lectures, prior to discussing why there are many successful Cellular Phone companies SOA Initiatives.  

I start my lecture by describing two new banks. I describe a very simple Business Plan and the Information technology effort supporting it.

The first imaginary bank, named T-Bank (T stands for Traditional) built Legacy Silo based systems. The students easily find and understand the disadvantages of that approach.

S-Bank(S stands for Service Oriented Architecture)imaginary bank as well,  built a pure Service Oriented Architecture and the systems building blocks are Services. The students easily find and understand the advantages of this approach. It is  relatively simple and easy to  build S-bank systems

The third imaginary bank is R-Bank (R stands for Real). It is a "T-Bank" which was merged with another "T-Bank".
Moving from large Silo systems architecture to SOA based Architecture is a long, complicated and expensive journey. 

Let us go back to the Cellular services companies. 
Which type of bank resembling them? These companies are new companies, therefore most of their systems are modern. They have only few Legacy Silo Systems. They resemble S-Bank.

Most of the Traditional Telco Companies as well as most Banks, Insurance Companies, Governmental Agencies and Utilities companies resemble R-Bank.

It is easier for Cellular Services Companies to transform their architecture to SOA, therefore SOA Initiative's success stories of companies of this vertical are common. 

New Challanges to Cellular Services Companies
Similar to the need of Trditional Telco Companies to reinvent themselves a decade ago, Cellular Services Companies need to change their Business model.  
Revenues from Cellular Phone calls and SMS messages are lower than few years ago.

Services like downloading a Ringtone you paid for are obsolete in Smartphones.

Regulations and Competition are factors lowering income from Phone Calls and other services.

Mobile Apps make some paid services unnecessary. 
WhatsApp is an example of an aplication replacing SMS, without any revenews to the Mobile Services provider.
Infrastucture costs are high. 

The Mobile Services Companies are looking for new revenews sources e.g. Financial services, Content Services and even Cloud Computing Services.

The lucky providers have solid SOA and BPM implementations, which facilitate the major IT systems changes supporting the assimilation of new Business Lines. 

Final Notes
SOA provides the basis for Business Agility. Business and IT Agility is a must for Traditional Telco companies, as well as new Telco companies, which have no choice but to reinvent themselves. 

I read about financial difficulties of Post companies.
Increased usage of e-mail, SMS as well as other technologies, reduce the number of letters and reduce the revenews. Soon they will have to reinvent themselves like the Traditional Telco services providers and the Mobile services providers.
  



  


Comments

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...