Skip to main content

Gartner says, Adapt to the new Delivery Models

And I called it myself, GDM (Global Delivery Model). Search my blog from it ;) Anyways...

The report, Alternative Delivery Models: A Sea of New Opportunities and Threats, says that IT leaders must explore these models or risk having business units implement the solutions without their knowledge and support.

Alternative delivery models require IT functions to acquire, package and deliver IT in new ways, the report said. “These alternative delivery models start from externals. Software-as-a-service is not something you buy and install in-house, it’s something you get from outside as available functionality, and you adapt to it,” said Claudio Da Rold, vice president and distinguished analyst at Gartner.


So this article really doesn't say much, but I can tell you a few things, where you should pay attention to and start adapting to:

  1. "Pay-as-you-go" models: That is the foundation of the SaaS, VaaS or even DaaS (data center as a service), where you copy all your infrastructure, and have it rested somewhere and it is intelligent enough to calculate and trigger several critical alarms, such as power usage, consumption, uptime, ROI, user response, profits and then allow the business managers to even "play" such scenarios, such as a Virtual environment, a simple subset of your data center, whcih you can run in your office. That way you can pre-run scenarios, that will pre-calculate all that critical information, and ask you to choose for facilities like a. Google premises in Poland, Amazon premises in Guatemala, Avastu premises in Kampala, VMware premises in Dalian etc. The pay-as-you-go model is the foundation of a typical "business agile infrastructure".
  2. "Use-and-throw" models : This applies to the test and development windows. You have to define, conceptualize, build, deploy, market, and tear down the virtual business units. A simple example is using simple, versatile, heterogeneous and agile data center tools such as openQRM (sorry about the brand name but these guys have a massive future in this area and will be the ones to watch!), it really amazes me that these guys are so deep and so broad in their product planning. Anyways, the whole idea is to have this component equally agile, to help businesses adapt to the continuously changing, or better said increasingly declining "business windows".
  3. Virtual employees: Forget about the traditional employees. forget about the ones that drive miles to come to your office. forget about getting jobs where you need to sit and "show you face". you will have a typical multinational teams that will sit together in a virtual rooms. They basically sit and home and meet occasionally at conferences, bootcamps, roadtrips etc. You cannot imagine how productive the folks will be.
  4. "Do-it-yourself" Models: The amazing thing about globalization is that , we started sourcing stuff around the world that could be easily done such as call centers, reservations, credit cards etc. India has greatly benifited from such models, but with virtualization and the self-service model, things are about to change. It ws funny to see the Indians learning to speak in the american accent, while I argue this, why would you need a human behind an activity that is easy to automate? Having said that, this simply means that the "virtual employees" around the world can elevate their operational levels to do more intellectual and useful things like "swarm research on alternative fuels!". Getting back to the topic, "self-service" models, like that of IKEA which are flawless and successful, will be used for mundane activities (depending upon what we will call a mundane activity as we all advance towards "advanced citizenry").
These , and more, models will help business get into more of a defining and tearing down LOBs without much overhead, without painful firings and outsourcings. Disruptive technologies and trends, such as sourcing (in- or out-sourcing), create a sense of insecurity and may seem to threaten our stability, but we all need to understand that these are merely "tools of change" and no matter how bad and evil they look, you can almost compare it with a change that you have to go through when your parent forces you to get into the water and learn to swim. It's scary in the beginning but at the end of the day, it is you who is gleaming back with confidence!

Enough for today ;-), here's the link that made me elaborate on what they may have meant.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op