The Next Evolution of IT

IT as a Service

Subscribe to IT as a Service: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get IT as a Service: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

IT as a Service Authors: Elizabeth White, Pat Romanski, Ed Witkovic, Alan Williams, Liz McMillan

Related Topics: Cloud Computing, CIO, Cloud Expo on Ulitzer, IT as a Service, CIO/CTO Update, The Cloud Academy, Big Data on Ulitzer

Cloud Computing: Blog Feed Post

Is Your Cloud Strategy 3D-Ready?

Don’t worry, you won’t need to wear funny 3D glasses to read this blog

While the TV and consumer industry is getting ready for its next wave of innovation called 3D, the IT industry has been going through a similar three dimensional transformation. Let’s have a closer look at this 3D journey of IT and how a good cloud strategy should support all three dimensions. And don’t worry, you won’t need to wear funny 3D glasses to read this blog.

Cloud computing is not the first innovation to hit IT – although the amount of hype and blogs seem to indicate otherwise - ever since the first computer got carried into the building all the way to the latest generation of tablets, the way we use IT, the things we use IT for and IT itself has been changing profoundly. We can classify these changes along three dimensions: Extending IT’s reach to new users and into new functional areas, Abstracting problems so they can be managed at new conceptual levels and Sourcing solutions from specialists where it makes sense.

Dimension 1 - Extend your reach
Traditionally the computers and applications that IT managed were used exclusively by employees. For example general ledger and inventory systems were accessed by the bookkeeping and manufacturing departments. This exclusivity has long gone. Applications have extended their reach and are now directly used by customers, by employees of partners and subcontractors and in some cases our applications reach out directly to suppliers or even suppliers of suppliers. This extension of reach has made IT a lot more time critical. Any failure can directly impact the customers’ experience.

Recent research into a phenomenon called WebStress shows how personal the impact of failure in what we traditionally called “business systems” can be. Consumerisation is the trend where people taking a more personal approach by bringing their own personal consumer devices into the business realm. Having business applications directly affect people personally is the other side of that coin. In many a mafia movie we heard the phrase “It’s not personal , It’s just business”, while clearly burning someone’s  house down or putting a horse’s head in his bed, has some deeply felt personal implications. Likewise the impact of business applications today is felt as personal. Not being able to get into your email, reserve as specific flight or be able to make a payment, directly impacts how people feel. IT has become personal, affecting people’s life and well-being. Organization’s are very much aware of the resulting lower tolerance –among both internal and external audiences- for any failure or downtime and service assurance is rapidly becoming a critical capability.

In some cases the line between what is the business and what is the supporting application is even blurring completely. For many people banking is their home banking application, the service the travel agent provides is an application to book tickets and hotels and Telco’s run software to connect people. More and more the digital process is the becoming the business process itself.

Extending the reach of applications also has a severe impact on who should be given access to our systems and applications. From a ‘simple’ list of employees with their roles and responsibilities we are moving to a situation where the list of potential users is endless. Security is becoming less about keeping people out and more about enabling the right people to do the right things with decisions about who and what are allowed taking place at increasingly granular levels of detail and subtlety.

The inherent network orientation of cloud computing provide a natural fit for enabling “extend your reach”, but “extend your reach” goes beyond having more and different people accessing ITs’ applications. It is also about extending into completely new application areas. Recent examples are convergence of traditional data processing based IT with voice and video and ventures into “big data”, where analysis of volumes of information - traditionally to large or too diverse to sensibly process - leads to new insights and advanced levels of optimization. These applications go far beyond the “traditional business IT” applications that essentially were limited to capturing and processing administrative facts about business processes, with processing that seldom became more complex than adding and subtracting and the occasional multiplication.

Cloud computing can help IT extend into these new , more complex, areas, but also there cloud computing is just another step in a transformation that started a long time ago. A transformation along a second dimension we call “abstraction”.

Dimension 2: Abstraction - IT moving up in the food chain
When IT first started, companies could not buy computers, they had to build their own. Later on computers could be bought but they did not come with any applications or even an operating system.  Customers were expected to build these themselves, first in assembler, later in higher level languages, while nowadays many complete standard software applications are readily available. The point is that IT for years has been using abstraction to move from extremely technical detailed work to higher level tasks.

Abstraction is basically the mechanism that makes modern IT possible. If we would still be required to manually manage every transistor on a modern chip, every register in a CPU or every disk in a content management system, IT would never get around to actually helping the business.

Abstraction occurs in programming, hardware and management. In programming we went from assembler via 3GLs and 4GLs to modern Object Oriented languages, where abstraction basically is the core concept. In storage we went from addressing blocks and spindles to disks to NAS or even content management systems. Similarly virtualization allows us to abstract from the underlying (detailed) physical implementation to a more standardized high level representation. And also in IT management we abstracted from managing individual components such as network, storage and processing to managing at higher conceptual levels such as services (ideally using some kind of service model).

Automation providing Abstraction
Abstractions have been around forever (in fact any spoken language can be seen as an abstraction describing underlying realities) but in IT they are often implemented through automation. We enable users to abstract to the higher level by “automating” all the tasks they traditionally had to execute at the lower level. Traditional programming was all about memory management, higher level languages take care of this automatically. Traditional data-processing was about running hundreds of sequential jobs across many sets of data in the right sequence, workload automation suites automated this away. SOA (Service Oriented Architectures) offer services that perform complex tasks “as a service” automatically. These services free the developer from having to manage or even understand the internal workings of the service he uses. Likewise traditional datacenter management was about provisioning and starting and stopping machines, while datacenter management suites (a.k.a. private cloud solutions) can automatically take care of this complexity based on preset rules and utilization levels.

Automation is the engine that enables the user to manage processes at a higher, conceptual level. Having the right conceptual model is essential to success. Conceptual models come in many shapes and forms. A file system is such a conceptual model, so is a database. Programs, applications and services are another example of conceptual models covering different levels. A good conceptual model is close to the reality the user wants to manage and allows him to specify in the appropriate level of detail what the solution needs to do. Appropriate is the key word here. Assembler language does not provide a good model to implement General Ledger or CRM systems, but could be appropriate to define operating systems or microcode.

Appropriate cloud abstraction models
Traditionally conceptual models for new technologies closely resemble the old reality; remember how the first cars closely resembled carriages, but without the horses. Cloud computing is offering new levels of abstraction – moving detailed management concerns out of the realm of the user – but is in many cases cloud computing is still in search of the appropriate conceptual models to be managed through. For example: a database provides higher levels of productivity because it allows us not to have to worry about detailed puts and gets across its file system, an infrastructure as a service cloud should offer a model appropriate to what the user wants to accomplish. If the user’s role is providing test and development machines to developers, having a (virtual) machine based concept can make sense. If his role is to run applications that provide business services, a more appropriate model would be based on services not underlying machines.

In a similar fashion the industry will have to find conceptual models to manage the use of SaaS and PaaS cloud offerings. Initially people will try and manage these in the same was as we managed in house applications and development platforms, but over time we may move to higher more appropriate levels of abstraction. An interesting development here is the Service Measurement Index (created by the SMI consortium in cooperation with Carnegie Mellon University and hosted at that aims to abstract the provided application services into a number of core characteristics that enable management at a higher abstraction level.

Dimension 3: Source - Divide and Conquer
The third dimension that IT has transformed itself along over the years is the sourcing dimension. As IT organizations moved on, they started to subcontract, outsource, offshore, procure as a service more and more tasks they traditionally did in-house.

A very old example of humor in Amsterdam goes as follows: A slightly intoxicated drunk walks down the Ferdinal Bol street when he sees a man high up on a ladder cleaning windows. He calls up “Hey, you’re doing that wrong”. The man comes down from the ladder and asks “How so?” The drunk quips “You should get somebody else to do that!”
“You had me come down all the way from that ladder for this?” says the man and punches the drunks light out. The moral of this is not that discussing outsourcing with the people actually doing the work is not a good idea (although true). It is that having other people do the work only makes sense if they are somehow better at this, if it is their core business or core expertise. This was true for outsourcing but also for cloud computing and it is no surprise that many of today’s cloud providers are extremely specialized or even monolithic.

To some extend abstraction and sourcing are related, they both result in the organizations not having to perform certain task themselves. But the two dimensions also tend to reinforce each other. The external providers perform their specialization at such scale that they are best equipped to automate their services up to a next level of abstraction. Many organizations that outsourced their service desk operations found that the provider rapidly moved from a chines army approach - where they processed millions of tickets manually - to offering automated remediation and self-service to make the support process more efficient. In-house teams simply did not have the time, skill or scale to do this.

Sourcing also means letting go of control, no longer being able to step in and fix things yourself in case things go wrong. As a result any sourcing strategy should include an exit and a fail-over strategy. One CEO became acutely aware of these sourcing risks when he read about several companies ceasing service to Wikileaks. He asked his IT department how dependent they were on the IaaS (Infrastructure as a Service) vendor the sourced their capacity from. His IT department - always game for a good challenge - took up the gauntlet and 48 hours of non-stop programming, gallons of diet coke and tens of pizza boxes (containing cheese and salami, not CPU’s) later they had created the ability to automatically move their complete operations to another IaaS provider.

Given the criticality of today’s IT from a business and personal perspective, every organization should consider such a divide and conquer strategy. By dividing the workload across multiple vendors or storing a shadow backup copy of critical data at an alternative vendor they can arrange instant failover and prevent themselves from being locked in.

Cloud computing has a distinct sourcing angle. In fact so much that many people see cloud computing as basically as just another form of outsourcing. But the attractiveness of cloud computing is that it can further IT along all three dimensions. Extending ITs reach to new users and into new functional areas, abstracting problems so they can be managed at new conceptual levels and sourcing solutions from specialists where it makes send.

Such a 3D Cloud strategy enable you to Extend, Abstract and Source Your IT, something us acronym crazy IT folks maybe should call EASY IT.

Read the original blog entry...

More Stories By Gregor Petri

Gregor Petri is a regular expert or keynote speaker at industry events throughout Europe and wrote the cloud primer “Shedding Light on Cloud Computing”. He was also a columnist at ITSM Portal, contributing author to the Dutch “Over Cloud Computing” book, member of the Computable expert panel and his LeanITmanager blog is syndicated across many sites worldwide. Gregor was named by Cloud Computing Journal as one of The Top 100 Bloggers on Cloud Computing.

Follow him on Twitter @GregorPetri or read his blog at