Once upon a time there were grammophones. Then came desktop-sized cassette players, followed by Walkmans. Of course,...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
many more variations of cassette players came in between. But the fact is that all of these innovations lead to what we call today an iPod. And this cycle of innovation continues to evolve.
Many such innovations exist. Another good example would be telephones. There used to be the old wall mounted telephones, and from those came the standard telephones that we used to see in the 80s and early 90s. Then came cordless phones, followed by mobile phones.
What do these innovations have in common? If you take a close look, you'll realize that as the technology evolved, it helped people go "Mobile." Audio/video-based mobile devices like iPod help people carry their choice of documentaries, daily news, lectures, music and so on and so forth along with them wherever they go. In the case of telephones, mobile technology enables freedom and flexibility beyond the walls of home and/or office. And in both the above-mentioned cases, the objective was the same – more flexibility to keep up with the changing way of life. In the former, iPods have helped information/music go mobile, and in the case of latter, cell phones have helped communication go mobile.
What was possible 100 years ago, we are able to do in a totally different manner today. I guess that's what we call "innovation."
One major difference between then and now is that the cycle of innovations has become faster and shorter. Innovations can be generally categorized as horizontal innovations and vertical innovations. Horizontal innovations take place in a sequence. At every previously unknown point, a new innovation is born. The birth of a new horizontal innovation always comes with the potential to trigger a vertical innovation.
With every horizontal innovation, which occurs over an interval of unpredictable quantum of years, a vertical process innovation is taking place to exploit the horizontal innovation that has already come into effect. For example, Walkmans have transformed into iPods; this could be termed as a horizontal innovation. Once iPods hit the market, Podcasts were born. This has opened up a plethora of opportunities for vertical innovation. Similar innovations have happened with mobile phones as well. A lot of value additions that was not possible with our traditional telephones are available now and this could also be termed as a vertical process innovation.
Innovation in the field of information technology
Let's take this concept of horizontal innovation and vertical innovation and apply it to the IT industry. It all began with the concept of mainframes. Innovations in networking triggered the next major leap in horizontal innovation giving birth to client-server architecture. These technological innovations lead to numerous vertical innovations.
Organizations started developing applications around this network architecture until it reached a similar point to where the traditional telephone gave birth to the mobile phone. Like the features and flexibilities that came along with mobile phones, IT also started demanding for such features and flexibilities that are critical in nature, because the businesses started demanding it. That demand gave birth to the next and the current technology, which is, service-oriented architecture (SOA). Vertical innovations have already started taking place around this technology and this is where organizations like SAP, IBM and Microsoft are already taking a lead role.
But there is a marked difference between the innovations that came with the previously mentioned examples (phones/iPods) and SOA-based innovations. The bottlenecks that came with past innovations were quite challenging, because any further innovation to the core itself demanded a total abandonment of previous innovations, whereas the SOA approach deviated from the path. SOA was flexible enough to adapt to the changing business needs.
Let's take the example of mobile phone; if someone wants to have more features built into an existing phone, they'll be forced to abandon their existing phone and go for the latest model that is available in the market. In the SOA world, if an organization decides to change the way it does business, it can incorporate that change into the existing Web services (A Web service is nothing but a program that can talk to another program). Web services enabled a huge step toward flexibility across heterogeneous landscape. But this approach was not sufficient to unlock the true potential of Web services. Most of the Web services expose the functionality of individual applications and are too fine-grained to be efficient building blocks for an enterprise-wide business process.
So to sum up, SOA brings in a great degree of reusability that is generally not available with other innovations and lowers the TCO to the end user.
In the client-server world, technologies behave more or less like wired/cordless phones. Businesses did not have the flexibility to stretch outside the four walls of organization. And if they were able to do so, then it comes with a huge implementation cost and limited flexibility. Security and reliability become a burning issue. Above and beyond, the biggest challenge for IT comes from rapidly changing business processes, which force IT to deliver something that is malleable and ductile.
That is exactly what SOA intends to deliver. Breaking the four walls was of top priority; when that was achieved using a Web servers / intranet / Internet combination, the next objective was set at breaking down the business process into discrete logical units. It is these smaller units of process that was later on used to build a complete process. Having arrived at smaller units of business processes and the kind of flexibility that has come along with it, let's take a look into how SAP benefits from it by bringing in another example.
Let's look at how people used to make travel arrangements in the past and analyze how they do it today. In the past, when someone decided to travel, they ended up carrying out different aspects of travel-related activities at different locations at different times and in a different sequence. For example, a particular individual might go to a travel agent to get his tickets and visa arranged. Then he might proceed to a totally different vendor to get the best deal on a hotel. From there he'll go to another vendor to get his foreign exchange done. He may even rely on a different agent to get his ground transportation arranged.
The list can go on and on. But today all travelers have to do is log on to a Web site and get everything done in one spot. One may book tickets, make hotel reservations and get foreign exchanged arranged and also get a choice of ground transportation arranged in single location in a more organized and in a well sequenced manner.
How is this all possible? Let's drill down a little bit further.
In the past when someone decided to travel abroad, that person would try to make most of the travel arrangements while in her hometown. Once she reached her destination, she'd try to take care of her ground transportation, get the best hotel deals and gather weather information etc. This is primarily due to issues like language barrier and inability to get proper information from the hometown. If, lets say, someone from Germany decided to travel to India and decided to make a phone call to a hotel in India, one cannot expect to have a German-speaking customer service representative attending telephone calls from hotels in India. This makes booking a room a cumbersome process. The same can be applied to car rental, weather forecasting and getting other important information pertaining to travel needs.
Times have changed drastically; there is no language barrier anymore. Any person from any country can communicate to anyone in the world using the latest of technologies. That is exactly what Web services do. Previously every industry worked as silos. When I say silos, I meant to say a travel agent only dealt with issuing airplane tickets, a foreign exchange dealer only dealt with converting currencies, car rental company only dealt with cars. These silos never interacted with one another even though they are closely related to each other from a modern day traveler's perspective.
In their quest to deliver the best to their customers, travel agents tried to integrate these different silos together and started seeing it as a great value addition to their customers. Once again, that's exactly what Web services do. Telephones and faxes (later on emails) don the role of integrating silos. This approach was working well for sometime, and then came the demand for more transparency of process that was going on between the two silos. Even more challenging was the effort to maintain an already existing relationship between the two business entities and then add/delete/modify a business entity from another (e.g., between a travel agent and a new car rental company).
Meeting such challenges was never an easy task. As business needs change more frequently, there was always a need for the technology to adapt to that change without becoming a bottleneck to the businesses. SOA became a flexible solution for most of the above-mentioned constraints.
So how did Web services manage to overcome this crisis?
Today more and more businesses are moving towards SOA. In the SOA world, discussions are mostly based around Web services. Web services became the fundamental building blocks of SOA. A Web service could belong to any domain. A group of related Web services helps to meet certain business objectives.
Let's take this understanding and apply it to the travel scenario we have been discussing so far. A travel agent will expose an external facing portal to its customers, who will also have the ability to interact with a car rental company, a foreign exchange vendor, a weather reporting agency and so on and so forth. This will make the customer feel extremely satisfied, because it help them plan and execute the entire trip from one single portal. They are not aware of behind the screen integration.
Businesses started offering their services in the form of Web services. If any other business needs those services to add value to their businesses, all they have to do is just integrate them with their portal/application. This will also bring in the much needed transparency to business. What was not possible previously suddenly becomes possible and extremely simple to deal with. For example, if there is a need to track the car booking that he/she has made, a customer can do it from travel agents portal itself. SOA gives the flexibility to access this critical piece of information from each other's database without compromising each other's security. The biggest advantage comes from the fact that, based on changing business scenarios, businesses can enhance their Web services within a very short span of time without disturbing their existing applications.
What has this got to do with SAP?
SAP started off in a similar manner. SAP built its applications as silos. SAP has a range of applications like ERP, CRM and PLM etc. (to name a few). Today's complex business process demands flexible and efficient communication between these silos so that the end users are able to make informed decisions. Existing communication was not flexible enough and managing data between the two silos became extremely cumbersome and lacked security and transparency. In an attempt to overcome these shortcomings, SAP decided to go the enterprise SOA way and made Web Application Server its underlying platform. SAP started converting all its time-tested business processes into enterprise services. Once an enterprise service, any silo can start accessing another's enterprise services seamlessly.
SAP uses NetWeaver technology to make this client server to enterprise SOA transition a comfortable one. In other words, SAP's answer to the complex world of silos stitched together using enterprise application integration (EAI) was to go for the enterprise service-oriented architecture (enterprise SOA), which is nothing but an open architecture for adaptive business solutions, enabled by SAP NetWeaver. Enterprise SOA complies with the service-oriented architecture standards, enabling both flexibility and business efficiency by lowering the TCO. With enterprise SOA, businesses can innovate new applications by extending their existing applications.
With this in mind, lets take a look at how SAP's order-to-cash scenario can be achieved using enterprise service-oriented architecture.
In an enterprise SOA world, a composite application will consume relevant enterprise services to automate the flow of information from application to application that is otherwise sitting in different silos. A role-based interface will ensure that every user from a business context gets access only to those information and functionality that are required to carry out their objectives. SAP NetWeaver that is sandwiched between composites application and enterprise systems such as (ERP, CRM, SRM, etc.) will contain all the process. These processes are defined, implemented and controlled at a business level with SAP NetWeaver providing the environment to build enterprise services that control the flow of information from one application to the other.
Abdulla Fawzi has over 14 years of experience in IT. He is currently working for Siemens Information Systems Limited as a consultant.
This content is reposted from the SAP Developer Network.
Copyright 2007, SAP Developer Network
SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free.