Framework to calculate TCO for Cloud Computing and Virtualization

To my fellow architects -

A lot has been said about how elastic computing or on-demand computing or cloud computing can be a great cost containment vehicle for companies. The key element there is the pay per use costing model of each of these concepts. If an enterprise is able to predict it's work load and it's usage models then these computing concepts make a lot of sense. The question not withstanding issues such as security, the need to control the deployment environment etc. is in regards to whether these elastic computing models truly deliver on the promise of cost savings and/ or cost avoidance.


Has there been a proven way of calculating the TCO for traditional investment in IT assets that could now be used to compare and contrast the advantages or to identify the hidden costs of these pay per use computing models? I am wondering if there have been any frameworks that exist for doing a cost benefit analysis for even concepts such as Virtualization and Grid Computing.  What are some of the elements that need to be plugged into this TCO model to truly get to an accurate figure? Do you include costs associated with "loss of control" and/or "lost business opportunity costs" due to the inability of the cloud provider to scale up an environment during your peak? Is there a truly scientific and proven mechanism, methodology or process that could be used to compute TCO for these newer computing models?

Thanks in advance for your help.
surekha -

Comments

  1. UnknownJanuary 25, 2011 at 6:10 AM

    Surekha -

    Yes, there has :) But by definition, it can't be 100% truly and purely scientific, because we're not just talking about technical capabilities - we're also talking about organizational, business, and risk capabilities.

    So the answer is three-fold. Yes, elastic computing models deliver cost savings in the near to short term. And no, there's no such thing as free lunch - over a standard benefits case term of 3-7 years, the total cost of ownership (in cash flow terms) is likely to be higher with an elastic model. The last bit is perhaps the most interesting, and falls under the "Caveat Emptor" category. While the capabilities delivered by an elastic compute model are similar from organization to organization, the specific required levels of investment in each of those capabilities are different (if they are aligned properly with business objectives.) So it's possible to build a "one size fits all" CBA at the capability level, but not at the instance level for each organization.

    Aleks

    ReplyDelete
  2. digital certificatesJanuary 26, 2015 at 12:28 AM

    Grateful to check out your website, I seem to be ahead to more excellent sites and I wish that you wrote more informative post for us. Well done work.

    ReplyDelete

Post a Comment

Popular posts from this blog

Issues with Server Virtualization

Virtualization has been considered a great way to maximize utilization of server resources by increasing server density. In addition, this concept is considered to be very key to green IT initiatvies as it reduces the number of compute resources needing to be supported in a data center thus reducing the cooling and power costs. Having said that, there seems to be a performance downside to virtualization. Given that a virtual machine (VM) is yet another layer of indirection the server HW this layer negatively impacts the performance any time there is a need for the application to access IO Channels, SAN disc and other network resources. This is especially so when the application code is either running inside of a JVM or an application server container such as a JEE container, .NET CLR or even a web server servlet container. In all cases, performance profiles of an application seem to vary whether the application is running inside of a virtual layer vs. directly on the physical server. V
Read more

Data Aggregation & Data Discovery - Part I

A lot of talk has been heard lately about the concept of data lake.  Variously known as, data refinery, data factory etc.  I find it interesting that we now hear logical architectural terms that speak to the concepts and to the purpose of the big data technologies such as Hadoop / HDFS and Apache distributed database technologies such as HBase / Cassandra .    This may be indicative of a shift.  What I am not sure of is does this mean that there is a level of maturity that has been achieved by this suite of open source technologies? Or could  this point to the fact that these technologies have practical applications that solve enterprise scale problems? Or does it show that enterprises have realized that they are no longer able to just deal with "structured data" and that a vast majority of information lies in the space of "unstructured content" leaving them no choice but to venture into the realm of big data technologies?  Not really sure!   The fact re
Read more

What is the definition of a strategic partnership with a vendor?

In this post I try to outline a few features of what I would consider a strategic partnership with a service provider or a technology vendor.  These are thoughts that I have distilled from years of experience (good and bad) with my vendor partners.  Hence this aspect of doing business cannot be overlook and not the least of these is the "cost" of doing business. Here are a few key attributes, not necessarily in any particular order of preference. 1) the strategic partner relationship has to go beyond a transactional one to that of a more long term one 2) the strategic partner has to have skin in the game - they have to be measured with your success criteria - they can succeed only if you do 3) the strategic partner has to be willing to "share" their technology roadmap with you 4) the strategic partner has to allow you to re-shape their technology roadmap to meet your needs 5) the strategic partner relationship has to include making their test labs, test gear, pr
Read more